4 ms·

I'm not blaming the file, i'm saying that using a hammer as a drill is silly, and that it's not the screw nor the hammer's fault, it's the user's. Atom was des

I'm not blaming the file, i'm saying that using a hammer as a drill is silly, and that it's not the screw nor the hammer's fault, it's the user's. Atom was designed as an editor for web developers. They took some trade offs when building it, and because of that opening large files is difficult for it. When I need to open large files, I use tail, or ed, or notepad++, or just grep or something else. It's not that the Atom programmers couldn't implement it properly (FFS they built github, i'm sure they know how to open a file without using 1GB of memory...), just that it didn't make sense to for the usecase atom was meant for. But it doesn't seem like i'm going to convince you, so I guess we can agree to disagree!

castis 9y ago
> I'm not blaming the file, i'm saying that using a hammer as a drill is silly, and that it's not the screw nor the hammer's fault, it's the user's. 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.
- Klathmon 9y ago
  >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!
  - castis 9y ago
    > If it's different for you, then Atom might not be the best tool for you! Likewise for tools that imbue the user with a blind eye and patronizing tone.
rplst8 9y ago
> I'm not blaming the file, i'm saying that using a hammer as a drill is silly, and that it's not the screw nor the hammer's fault, it's the user's. Except in this case, we're comparing two hammers - just different brands. If we were trying to use Microsoft Word to code, you'd have a point.

castis 9y ago

> I'm not blaming the file, i'm saying that using a hammer as a drill is silly, and that it's not the screw nor the hammer's fault, it's the user's. 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.

Klathmon 9y ago
>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!
- castis 9y ago
  > If it's different for you, then Atom might not be the best tool for you! Likewise for tools that imbue the user with a blind eye and patronizing tone.

rplst8 9y ago

> I'm not blaming the file, i'm saying that using a hammer as a drill is silly, and that it's not the screw nor the hammer's fault, it's the user's. Except in this case, we're comparing two hammers - just different brands. If we were trying to use Microsoft Word to code, you'd have a point.