4 ms·
Atom's performance problems are not because of Node, they're because they render with HTML, loading your whole text documents into the DOM as hundreds of thousa
by BillinghamJ 11y ago
Atom's performance problems are not because of Node, they're because they render with HTML, loading your whole text documents into the DOM as hundreds of thousands of separate elements.
Using Node JS as the backend to a proper native rendering system would work fine, and in fact if the application was written to properly handle everything asynchronously, it may well be faster than an app written entirely in the native language of the system.
- Tiksi 11y ago> it may well be faster than an app written entirely in the native language of the system. So nodejs is now faster than C/C++? I guess Javascript really can do everything.
- BillinghamJ 11y agoNo. I said it "may well be", because a naive implementation using a native language may block while doing IO and be less responsive, unable to do other things while waiting for external stuff to happen. Perhaps I should have said "may well be more responsive than".
- hollerith 11y agoSo, you don't actually know anything about whether native apps block on IO? (I doubt they do on any modern version of Windows, OS X, Linux, Android, iOS or Windows Phone.)
- BillinghamJ 11y agoDepends entirely on the developer. Most APIs support both non-blocking and blocking.
- p3llinor3 11y agoHonestly, I've never had a problem with Atom's performance. The only time it comes up is when one opens an extremely long file which contains one extremely long line of code.
- teacup50 11y agoSo "never" isn't actually true.