3 ms·
I do enjoy using Atom as an everyday editor for ECMAScript / React apps, where the convention is to have many very small files. ES6 + Hasklig font + Ligatures m
by dawidloubser 11y ago
I do enjoy using Atom as an everyday editor for ECMAScript / React apps, where the convention is to have many very small files. ES6 + Hasklig font + Ligatures make for a particularly visually-pleasing coding experience.
Unfortunately, Atom has severe performance issues with files that are anything above "tiny". For example, a 500-line XML file will lock Atom up for many seconds, to several minutes, while it's inefficient little ECMAScript parsing engine tries to chew through it. I build the latest version almost daily in anticipation of improvements in this area!
This is what prevents my adopting this otherwise lovely, vibrant, flexible editor for all my tasks.
A real IDE like IntelliJ has no problems with applying various tooling (parsing, validation, de-bugging of XSLT, etc etc) to a 15,000-line XML file.
In the longer term, I do hope that somebody is addressing this - which I think is literally the only thing that Atom has going against it.
- viperscape 11y agoI personally don't like the extension building aspect in atom. Extending emacs, or sublime is much simpler to me.
- Touche 11y agoPlease don't call JavaScript "ECMAScript", that name only exists for trademark reasons.