I closed Atom and my memory pressure dropped considerably. Installed Brackets and the pressure is still low even with Chrome and a box running yet.
This probably isn't an issue for people with 8+ GB of ram though, unless it actually has a memory leak.
Honestly, nobody who adopted Atom should ever be surprised by any single aspect of its sluggishness.
> 2. The huge editor software file size. I am not leaving
> 400mb for "yet another text editor"
I don't know why you'd care about this, besides reasons of dogmatic principle. Disk is the cheapest thing in the world. Any benefit that can be had at the cost of larger artifact size, especially for things like consumer applications, should be taken, IMO.Apple's Macbook SSD upgrades are quite a bit more expensive than you're positing.
I am pretty economical with space, I don't store media on here, it's almost entirely dev tools and code projects. And I do not want a piece of software that takes 400mb without providing me significantly more value than what my 30mb (Sublime Text) one. I don't care about media being large, or backups taking a lot of space, or installers being big, since I can shove those on an external.
But I'm obviously not going to do that with any dev tools. Any tool that cannot justify it's size cannot live on my internal drive, and if it ain't there I'm not using it.
1. The slow startup time in question
2. The huge editor software file size. I am not leaving 400mb for "yet another text editor"
3. I had become very dependent on some Sublime plugins for my work and the Atom counterparts were a long ways off being up to par.
The thing that first made me excited about atom was that being built around Chromium I thought we could finally have an editor with a nice Chrome-like web view with real-time update built into it, as a tab or something.
However, I noticed a thread on it in Atom (can't find it now), and it sounded like the core of Atom's security prevented such a thing from ever being built, so it would remain an unfulfilled desire. Oh well.