41–50 of 93 posts
Earlier quoted context omitted.
Unless they start using native code it will always be like that.
I went back to (non-native) emacs, partially due to this problem.
In contrast, Atom just uses native code as the JIT, and then not only does (almost) everything in JS but also renders it with slow DOM.
Earlier quoted context omitted.
It should not take an i7 processor to run a text editor. I mean no disrespect, but either something is very wrong with your computer, or something is very wrong with this software.
For years and years it took a very powerful computer to get decent performance out of Emacs. Emacs only seems speedy now because computers have finally caught up. Either Atom will get faster, or it will add so much value it's okay being slow. And then computers will eventually catch up, just like they did with Emacs.
Texteditors must be fast and predictable. Tab support for vscode was it for me. Also, their ide must add overhead and yet still much faster than atom
Earlier quoted context omitted.
Wholeheartedly agree. I just tested this new version out. I really keep trying to use Atom, but it's just unacceptable currently when compared to Sublime. Very slow startups and laggy. This new version takes 5-10 seconds before I can start coding, that's far too slow. With every update I keep hoping things are faster, but only marginally so. VS code loads in less than 3 seconds and is a lot more snappy. I don't under…
Why is waiting 5-10 seconds for your editor to open such a problem?
Also 5 seconds is enough for my attention to maybe wander. Not every time but often enough to waste minutes of productivity per day. It all adds up. Amazon found that each extra millisecond delay causes customers to navigate away from the page. It isn't laziness just human nature.
Earlier quoted context omitted.
Why is waiting 5-10 seconds for your editor to open such a problem?
For the same reason waiting 1-2 minutes for your laptop to boot is. Also because people often open/close tons of small files during the day instead of opening a project and working on it for hours. Plus, the slugginess extends beyond startup time, into working with large files (were large = puny for other editors' standard) and other activities.
It is a shame people don't value users time like this any more.
I have participated a bit in the Atom.io open source repository, but now I am back to Sublime. It's so fast and reliable compared to Atom.io.
Earlier quoted context omitted.
Wholeheartedly agree. I just tested this new version out. I really keep trying to use Atom, but it's just unacceptable currently when compared to Sublime. Very slow startups and laggy. This new version takes 5-10 seconds before I can start coding, that's far too slow. With every update I keep hoping things are faster, but only marginally so. VS code loads in less than 3 seconds and is a lot more snappy. I don't under…
Why is waiting 5-10 seconds for your editor to open such a problem?
Earlier quoted context omitted.
Why is waiting 5-10 seconds for your editor to open such a problem?
For the same reason waiting 1-2 minutes for your laptop to boot is. Also because people often open/close tons of small files during the day instead of opening a project and working on it for hours. Plus, the slugginess extends beyond startup time, into working with large files (were large = puny for other editors' standard) and other activities.
It seems silly to me for someone to adopt a strategy of opening/closing Atom (instead of reusing an open instance) and then complain about how long it takes to boot. You don't park your car at red lights and turn off the engine, then complain about how long it takes to pull away when the lights turn green.
> Plus, the slugginess extends beyond startup time, into working with large files (were large = puny for other editors' standard) and other activities.
This I totally get. If this is someone's use case, they probably shouldn't be using Atom.
I don't mean to rail on you in particular, I just always found the "oh it takes so long to start" complaint to be a silly one. It's such a minor thing. Atom is really good for a bunch of use cases, it's a shame that people write it off for this stupid reason.
I have participated a bit in the Atom.io open source repository, but now I am back to Sublime. It's so fast and reliable compared to Atom.io.
I have participated a bit in the Atom.io open source repository, but now I am back to Sublime. It's so fast and reliable compared to Atom.io.
Also, its instant search across all files is quite amazing actually. Faster and more useful than any other editor I have tried
Earlier quoted context omitted.
For the same reason waiting 1-2 minutes for your laptop to boot is. Also because people often open/close tons of small files during the day instead of opening a project and working on it for hours. Plus, the slugginess extends beyond startup time, into working with large files (were large = puny for other editors' standard) and other activities.
When my laptop is booting I'm usually fetching coffee. Most of the time I just crack the lid, it wakes up, and all my editors are still running anyway. I probably boot an app like Atom once or twice a week. Plenty of tools I use (PHPStorm, vagrant boxes, VMware) all take way longer than 5 seconds to load and that has no noticeable impact on my productivity or happiness. It seems silly to me for someone to adopt a str…
> It seems silly to me for someone to adopt a strategy of opening/closing Atom (instead of reusing an open instance) and then complain about how long it takes to boot.
That's not what happens. They looked at the tool, stated it doesn't meet their needs, explained why, and then _did not adopt the tool_. The Atom folks can decide they don't want those users or they can address their abominable startup time, but you can't suggest "change how you do everything" and hope to win friends or users.