>Breaking your workflow in the name of progress seems counterintuitive.
Using another editor where opening large files doesn't break my workflow, but needing to alt-tab over to the browser to see how my changes look does is much worse for me. I look at log files every few days at most, and generally while they are on another system.
I look at the results of my development on my app hundreds of times a day.
If it's different for you, then Atom might not be the best tool for you!
No one is claiming the opposite. An appropriate argument is that some nails are bigger than others and this hammer in particular chokes on big nails.
> When I need to open large files, I use tail, or ed, or notepad++, or just grep or something else.
Breaking your workflow in the name of progress seems counterintuitive.
> I'm sure they know how to open a file without using 1GB of memory.
The realities of Atom prove otherwise.