[yAnonymous]

Are you using the latest version? I can hardly see a speed difference compared to VS Code anymore, even for big projects and files. It's certainly very far from being unusably slow.

>buggy software and the unresponsive devs

I mainly use VS Code for that reason. It does feel a bit more polished and Atom is missing some much requested features, most notably a list of open files in the sidebar (the plugins that offer this are all terrible).

[PeterisP]

Tried Atom for Mac right now. Opening a tiny (10k rows) csv file took multiple seconds, opening a larger (100k rows) csv put out a warning about potentially taking a lot of time and in a second simply crashed before loading it.

[yAnonymous]

Opening a CSV with 100k rows takes about 10s for me and is pretty workable with an i7 and 16GB RAM. Selecting and editing text is almost instant.

[madamelic]

...

And why should you need that kind of machine to do text-editing?

If a text editor can't open a big file unless you are on a beast of a machine, it isn't a very good text editor.

[yAnonymous]

A 5-year old i7 is far from a beast machine. You're a typical Apple customer that pays too much for an underperforming piece of crap and then complains about the performance.

[oconnor0]

My computer - a 3+ year old i7 - opens the 20 million line CSV from http://files.grouplens.org/datasets/movielens/ml-20m.zip in ST3 in about 25s and opens the 1 million line CSV from there in little over a second. 10s to open a 100 thousand line file on a modern machine is unnecessarily slow.

[yAnonymous]

I didn't say 10 seconds was fast and it isn't, but for the very few times I have to open files with 100k lines it's more than enough and far from unusable.

When you regularly work on such files, Atom is the wrong tool for the job. For regular programming however, I'd argue it's far better than Sublime Text by now.