I really wanted to give Atom a chance since it gets stuff like ligatures right, but I find its slow startup speed to be a no-go. I simply find in Sublime a much stabler experience and faster startup time, which makes it feel more productive.
I was very pro-Atom for a while. I've since packed up and moved to Vim and then on to Emacs with evil-mode.
I never had any performance complaints while I was actually using Atom, but a while back I made a mistake when generating a text file that turned out to be ~1.5GB. Luckily, it was just one mistake in the footer, so I could take care of it without regenerating the entire thing.
Without even thinking about it, I opened it up with Emacs, went to the bottom, made my changes, and got back out. About a minute later, I saw how large of a file it was and was suddenly even more impressed with Emacs than I had been.
Just for fun, I then tried to edit it with Atom. Nope.
I can get behind it on my *nix systems, where I find it fast enough, but I find it terrible on Windows, especially when it updates and I find myself with two versions.
ligatures in source code? It seems as soon as I use a non-fixed width font, then indenting and other code formatting becomes tricky. Bjarne Stroustrup uses a proportional spaced font in his C++ book and I hate it.
Okay then ... does look good ... I assume that normal ascii is used under the hood and that is what the lexical analyzer sees. I am open minded -- of course it has to work with emacs -- I am not that open minded ;)
It's just a font, the underlying text is still the same no matter what font you use to render it. In fact, you could set Fira Code (or Hasklig) as the font for your terminal and (as long as your terminal app can render ligatures) it would render in emacs or any terminal-based editor.
