If the core is really powered by JS here (and not just extensible via JS - I haven’t been able to research this enough to know how it works, it’s not exactly clearly stated in big bold print either), then I think it’s at a major disadvantage. What problem are we solving anyway? We already have “web based IDEs” too… So this will have extensibility and some other clever features? Ok…But that’s then nothing other people couldn’t implement with the flick of the wrist. Don’t get me wrong, a very large portion of the web is going to use Atom.io purely because it’s built by GitHub. …But let’s be clear… That is going to be the main driving reason why people use it. Trust in GitHub…And I must say that it certainly peaks my interest and I will also give it a try.
So if not CoffeeScript, then what? ES6 like asked? Node.js? Nope, not those either. You’re still talking about the same limitations. Python like SublimeText? Maybe…But it misses the goals of the authors, right? You want something more web native. You also want something that looks toward the future…And this is where I believe there were better choices (and who knows maybe they weren’t even known to the authors).
So my two cents?
I think Spark is going to really give Atom a run for its money too because it’s built by Google which also has a trusted name.
So I’m super excited to see all these new editors take off because while I love SublimeText and while it does everything I need (which begs the question what “problem” do these new editors solve? Not much of one really), I am always eager to try out something new.