[moron4hire]

That's not why Atom feels slow. You're running a machine that can run JS faster today than any machine could run C 10 years ago. There haven't been any major innovations in text editor technology in that time, none that would warrant such a huge slow down.

Atom feels slow because it's over engineered. They try to make everything run through the plugin system.

[giovannibajo1]

The point is not if JavaScript is fast or not (which btw it isn't faster than C++ or not even just as fast), but how many layers of abstraction JS has to go through to display stuff on the screen or do anything useful. Having to fight with DOM and CSS to do anything like syntax highlighting is effectively triggering execution of millions of lines of code compared to sublime text that does a raw win32 or Cocoa call.

Comparison with 10 years ago is also not so relevant. 10 years ago you didn't try to autocomplete through an average modern JS project where thousands of files are created on disk even before you create your first div. Data processing needs are outgrowing CPUs improvements by far.

IOW there's no way Atom is getting as fast as Sublime, because of the huge stack it is built upon. It might get fast enough though, but my feeling is that the discrepancy is actually getting bigger rather than smaller, as we evolve our average needs as programmers

[moron4hire]

There are more ways than just the DOM to render text. And I didn't claim JS was faster than C, I said JS on modern hardware is faster than C on 10 year old hardware. Yet we still managed to run text editors "fast enough" 10 years ago. Finally, I made the specific point to say that Atom is not a good example of what should be possible in JS.