Atom 1.25

Tree-sitter (intelligent code folding) looks really cool. While I am a big fan of VSCode, I really do not like their indentation-only approach to folding. It makes constructs like C switch statements impossible to fold correctly. Something like:<p><pre><code> switch( ) { case: break; case: break; } </code></pre> won&#x27;t fold at the braces, but instead will just collapse one case statement, and it drives me crazy. This is even with the C&#x2F;C++ language extensions installed.<p>Good job Atom.

I tried really hard to not switch to VS Code. Wasting huge piece of my RAM + randomly and REPEATEDLY crashes which ends up destroying entire settings, packages to newly installed state. I&#x27;m done with it. I&#x27;m cool with VS Code.<p>I really had hope when they introduced V8 Snapshots on 1.17, then I had exact same crash couple of days later. And memory management wasn&#x27;t better. I was even thinking about to replace my mac, because I was running out of RAM just by having Atom + Firefox + iTerm with rails server and console running.<p>It&#x27;s really annoying to have your editor, where you spend most of your day, your shortcuts, extensions, settings, theme, all got destroyed in a moment in the middle of the working day. And you have still have to keep working with fresh installation settings. Damn. Worse, although I&#x27;m aware of sync-settings, I keep forgetting syncing my settings as they are evolved with time and it still feels insecure to be in need of syncing stuff because you don&#x27;t know when it will crash for the next time.<p>Looking at the issues, assuring that I did a good decision by moving away from it.<p>This one is still open: <a href="https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;12255" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;12255</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;14909" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;14909</a> <a href="https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;14922" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;14922</a> <a href="https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;15443" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;atom&#x2F;atom&#x2F;issues&#x2F;15443</a>

To preempt the inevitable modern-editor performance flamewar, especially with the introduction of a new parser: Has anyone been compiling statistics on time-to-editable on app startup, non-trivial-project-with-a-bunch-of-tabs open, and standalone-file open, for different Atom, VS Code, and Sublime versions, on freshly-rebooted popular laptop hardware? The closest I can find is from 2016, and isn&#x27;t representative of large projects or code you&#x27;d find in the wild: <a href="https:&#x2F;&#x2F;blog.xinhong.me&#x2F;post&#x2F;sublime-text-vs-vscode-vs-atom-performance-dec-2016&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.xinhong.me&#x2F;post&#x2F;sublime-text-vs-vscode-vs-atom-...</a><p>All joking aside, it would be a fascinating analysis; all the rationales for browser performance benchmarks apply here as well.<p>(And also, kudos to the Atom team for the new tree-sitter parser - very cool stuff!)

I used Atom for a long time till I encountered VS Code - haven&#x27;t looked back since. The startup time and integrated terminal just make VS Code awesome

Every Atom release post is filled with VS Code fans talking it up, it&#x27;s like a law of nature on HN.

Atom is my go to editor now. It’s simple, it’s pluggable, and modern. I really like it.<p>I’ve been recently using it with FB’s Nuclide, but that’s such a massive suite of plugins, it might as well be a considered a derivative of it. I can’t recommend Nuclide. It’s bloated, and breaks a bunch of behavior from vanilla Atom, but it is the only thing that seems to get remote editing right. I just wish someone would get that piece out of put it as it’s own plugin.

Has anything been done to improve speed? I tried running it on my Surface Pro (dual-core i7 with 16GB of RAM), and it was unusably slow, ate up a lot of RAM.<p>I like Atom&#x27;s interface, but it&#x27;s such a resource hog. So I will continue to stick with Sublime.

I&#x27;m surprised they still suggest to &quot;store your github username and password&quot; locally when they could just as easily suggest to &quot;store your github username and auth token&quot;.<p>Even if it&#x27;s locked in my OS&#x27;s credential store, do I really want to trust a text editor with my passwords? Why not suggest the more secure option? How sure can I be that none of the atom plugins I use will try to steal it?

Does it have a proper Windows installer yet? Multi user, Program Files for the code, Appdata for the config, option to install extensions either for all users in Program Files, or Appdata for one user. You know, standards, and more secure when random programs can&#x27;t alter the files of your editor

I took Atom for a ride, found it slower than VS Code. Not converting for the time being.

I know how popular Electron is on HN, but once it&#x27;s on I really like Atom. From the first install it had sensible defaults for Python, JSON, XML, HTML, SQL which are my main stays. I even like the default colour scheme. Hopefully in time it can start a bit faster...but that&#x27;s all

Using Debian 9 and Atom currently. I used VSC for a little while but it became unstable. It would often refuse stdin. Maybe the issue was the vim extension, maybe not. Rather than troubleshoot, I went back to Atom and have had no problems.<p>I work with about five languages just fine.

I&#x27;ve looked at VS Code a couple of times, but the Ruby support wasn&#x27;t very good (syntax highlighting didn&#x27;t even work completely). Is it time to switch or should I stick with Atom?

(points gun) Say Visual Studio Code again. SAY VSC again! And I dare you, I double dare you motherfucker! Say Visual Studio Code one more time.

I use Atom for Rails development, because it has better Ruby on Rails support than VS Code.<p>However, I am sick to death of its excessive memory consumption. This morning it was using 1.5 GB of memory.<p>It&#x27;s a text editor for God&#x27;s sake!

Any reasons to switch back from VSCode?

Is 1.25 the number of TB of RAM you need to run it?<p>I&#x27;m afraid my workstation only has room for one Electron-based monster(Slack).<p>Hopefully the Rust re-write improves things.