5 ms·
Yep, I was using Atom for 6 months, I wanted to give a solid go. But now I am back to sublime text. I can't really put my finger on it, but sublime text is jus
by jbob2000 9y ago
Yep, I was using Atom for 6 months, I wanted to give a solid go. But now I am back to sublime text.
I can't really put my finger on it, but sublime text is just snappy and reliable in ways that Atom isn't. Got really tired of Atom lagging because I'm typing too fast, got tired of lockups and hanging. VS Code has very simillar issues too.
It was a nice experiment (can we do editors in HTML/JS?), but I'm convinced native is the only way to go for proper editing.
- pitaj 9y agoHave you tried VS Code? It's very snappy in my experience, much better than atom.
- jbob2000 9y agoYep, been using it for a month full time so far. It IS better than Atom, but it still has snappiness problems. The embedded console is great, but not as fast as just using command prompt, it just has weird laggy moments. Using the built-in Git is also laggy, there's a delay when you click to stage a file, really annoying. The search is really laggy too, when you do a search across your app, it locks up the whole window for a second or two. Microsoft also has this really annoying tendency to use icons for everything, every once in a while I find myself googling wtf these icons are.
- godDLL 9y agoneither is even bearable on a Raspberry Pi, or any old laptop of which I have many laying around the house
- rplnt 9y agoSublime Text works as a simple code editor as well, while Atom has start-up times not far from those of Visual Studio. Opening files in a running instance of ST is virtually instantaneous. Not sure if it is even possible with Atom.
- brlewis 9y agoWhat release of Atom did you use? I'm curious whether newer releases actually feel better. I'm an emacs user myself, but am looking at whether to recommend Atom to others.