4 ms·
Has anyone tried Atom recently to determine if any of these performance boosts have made enough difference to consider switching back?
by jastanton 11y ago
Has anyone tried Atom recently to determine if any of these performance boosts have made enough difference to consider switching back?
- asp2insp 11y agoI've been using Atom as my daily driver for Python, Golang, Rust, and JavaScript for several months now. Startup performance is bad (have not tried with 1.1 yet) but editing/scrolling/fuzzy finding are all more than acceptable.
- thejf 11y agoI don't have any hard numbers for you, but it feels as if it's improved by a lot. I had switched away from Atom precisely because of the speed issue, but switched back to it a number of months back and I haven't noticed any performance problems.
- d2xdy2 11y agoI just updated to Atom 1.1 on my early 2015 rMBP... still takes upward of 20 seconds to open up a project containing <5 markdown files and a `.git` containing <10 commits. Once its started, it lags quite a bit. I really _want_ to use Atom, but the performance just kills it for me.
- seanwilson 11y agoYou should report this as a bug I think. I've used Atom on a similar machine for large projects with large commit histories and it's never takes more than a few seconds to open.
- d2xdy2 11y agoI might do that, I just hate submitting bug reports without being able to really say where the problem is sort of coming from.