Just move on man. I used to be a big hater of Atom, but then I realized that I was not contributing on its development so I stopped being a "hater" and continue with my own life using another editor that actually works for my use case. As the parent comment says, Atom works for some people and that is enough for them to continue its development, I am fairly confident that it will never have the performance that a native editor has but it is workable as long as you don't do resource intensive tasks.

My computer is not powerful at all so Atom is obviously slow as hell and lags all the time, at first I thought I improved my typing skills because I was typing faster than the editor was displaying the characters, but that was obviously not the case. Most Atom users — or at least the most active users — use rMBPs with i7 CPUs and (maybe?) 16GB of RAM, I don't want to buy a computer like that just to use a code editor like this, I would do it for an IDE though; and even if I had a computer like this I would not want to give most of its resources to the code editor when there are more important things to spend the CPU / RAM on.

If your intention is to open a database dump then use a different tool, a proper log viewer or something like that, I don't even understand why would you want to use a code editor — even with good performance — to inspect a DB dump in the first place.

Suggesting to screw a nail or hammer a screw will lead to similarly unsatisfactory results.

Atom is for writing code, not viewing logs. We have tail and syslog and a thousand other tools for that.

Ok, so I'll open it in Sublime/Vim/Emacs, read it, close it, then continue programming in Atom.