Re:Sunsetting Atom
by gibbitz on Wednesday June 08, 2022 @03:11PM
(#31672506)
This is why I continued to use sublime text all the way up to capitulating to TypeScript. Code was slower because of all the intellisense. I've had Code freeze on me a few times. Something that I don't have happen in Sublime or Vim. If you have a lot of RAM and work on a current mainstream OS it may seem smooth, but it's still using 400mb of RAM. May as well use Eclipse or WebStorm FWIW. That said I'm using VSCode now too, but things can always be better :).
[ Parent
| on HN ]
Re:Sunsetting Atom
by galaxyLogic on Wednesday June 08, 2022 @04:50PM
(#31673904)
Part of it may be just Windows. I use Windows a lot to move files and folders around and the File Explorer is something I constantly need to wait on to respond. The Windows as GUI is not very responsive in my experience.
Re:Sunsetting Atom
by manigandham on Wednesday June 08, 2022 @05:24PM
(#31674437)
> "but it's still using 400mb of RAM"
Why does this matter? What is the point of saving RAM instead of using it?
Because all my ram is already consumed. I have a 16gb MacBook running only a browser, vscode, ms teams, and the docker containers for the app and I have no memory left so I see a spinning ball every time I change windows. Ms teams was the final straw. Slack was about 300mb but teams is now 700mb+
It matters because your program is probably not the only one running.
Re:Sunsetting Atom
by manigandham on Wednesday June 08, 2022 @07:26PM
(#31675793)
It’s a small amount and if you’re using it then it should take priority. Modern operating systems with SSDs are very good at managing memory anyway.
Re:Sunsetting Atom
by mckravchyk on Friday June 10, 2022 @10:04AM
(#31694395)
Once you exceed it some of the content will go to swap, which is going to slow down the system (and wear an ssd faster). 400MB is not that much though, for me Code usually takes at least 1.5GB RAM.