> It's like complaining that opening a 6MB file in windows took over 3GB on my system No, it's like complaining that opening a 6MB file in Windows took the res

> It's like complaining that opening a 6MB file in windows took over 3GB on my system No, it's like complaining that opening a 6MB file in Windows took the resource usage from 3 GB to 3.6GB (in absolute terms), or from 3GB to ~10GB (in relative terms). > Not to mention that a 6MB file is pretty fucking big for something like atom. Yes, I know, 6MB isn't "big", but for an editor which is designed to only work on source files which are AT MOST a MB, it's big. Where is this design decision documented? What was the reasoning behind it? I looked at the docs, and couldn't anything supporting this statement, which sounds ludicrous to me. It's 2017, an editor shouldn't choke on 6MB no matter what you feed it.