Atom 1.8 and 1.9 beta
blog.atom.io
blog.atom.io
Full disclosure: Every time I try Atom I decide to stick with Sublime Text, largely because Atom feels slow. I've never tried VS Code myself.
There's some discussion in this Atom ticket: https://github.com/atom/atom/issues/10188
If you look the settings in Atom, it tells you specifically how many milliseconds each plugin adds to startup time. They REALLY add up. Install even more plugins to customize your editor, and it rapidly enters IDE bloat territory.
All that being said, VS Code recently launched a plugin marketplace of its own. I've installed Vim emulation and a couple of others, and really haven't noticed any increase in startup time.
I still wouldn't switch to VS code because by design[1] you can't open multiple folders in the same window, which destroys my workflow.
I can't imagine going any slower...
EDIT: yep, things have improved: https://github.com/atom/atom/issues/307
But, yuck, sounds like I should keep using VS Code anyway. I kind of want to be able to use Atom, but 2 MB is a frighteningly low size limit.
VSCode works great, completely replaced both Atom and Sublime for me. Give it a shot sometime.
Latest update added an on-screen terminal view, which is definitely useful for a quick npm install, etc. Some of the "solution" stuff is a little clunky to get setup for a full project, but it's interesting the approach MS is taking on this compared to classic VS. Hoping it gets a bit better on integrated project tooling for the likes of getting some of the boilerplate setup. Seems that go, python, C#, JS and TS are very well supported (out of the box or via extensions).
Disclaimer: I work for m-dollar. My commission rate is 0.0% and VS Code is free, so I am hoping to make it up in volume.
https://github.com/Microsoft/vscode/issues/1690
This glaring omission combined with the proposed performance improvements in the Atom 1.9 beta might just be enough to tempt me back to the Atom side again.
It's newish but very stable and uses Lua (not Javascript) as the extension language. It is very lightweight and faster than Atom.
Disclosure: I'm one of the contributors.
Do you mean the normal file browser or the recursive search (`ctrl_s`)? I did find Atom a bit lacking for general quick file browsing as well as previewing and usability of things like replace commands.
Do you know how Emacs handles too many recursive listings? Howl just truncates the search after 3 seconds and I'm wondering if there's something better we can do.
https://github.com/howl-editor/howl/issues/68#issuecomment-1...
I'm wondering the same every time someone writes VS Code is faster than Atom (which is true in my experience): yes, but why?
Everything you do in Sublime is done instantly. Try opening the command panel (ctrl+shift+p) both in sublime and atom. At least a 300ms difference. Multiple cursors, switching to different panels (I can see the whole pane getting rendered in front of my eyes -- not instant!), even things like loading the list of installable plugins or installing a plugin is far, __far__ faster in sublime, assuming package control, compared to Atom!
Sublime also has this insane feature where no matter how many plugins you have installed, Sublime will still start up in about 200-300 milliseconds, as fast as notepad on Windows and faster than gedit on linux. Atom only goes slower and slower and slower the more plugins you install.
When you're used to an editor that does everything instantly, everything that takes longer than 200ms takes too long.
I am a Sublime user. Your comment has moved me to register my copy now. (I'm serious!)
End d up with brackets for a long time but as much as I hate atom. It's where the plugins at. :(
Opens instantly in Atom for me.
You will notice the difference!!11
So I'm fairly hopeful for Atom. It took years for Sublime to get to where it is today, and Atom looks like it's on track to be a great contender. ... Until then though, I'll still cherish Sublime as my go-to text editor: it's got a well earned head start.
For example, you still can't move the sidebar to the right side after all these years.
A wrong file could be something too big for Atom to open, or just a smallish XML file with all of its contents on one line. Either will lock Atom for a while on a high-spec MacBook Pro.
Other than that, I agree it's pretty fast for most things.
Maybe it is because of the extensions I installed but they were all popular. If so then Atom should track crashes and correlate with extensions or something like that.
This beta version of Atom introduces several important changes that will bring performance and reliability improvements to the editor, as well as some new features we are really excited about. We recommend you check it out! :sparkles:"
I don't know if that means it's fast enough to replace other editors now, but it's promising.
The only excuse you can is 'but it's Foss'.