head -10 myfile.json
And that's exactly one of it's problems. It's not designed to be a damn text editor. Instead - it's just another "hipster editor". You can find a growing number of useless plugins, but can't open log file sent to you, or connect via proxy without a trouble.
Not to mention the speed and ram usage. My IDEA instance with a large project opened up use less memory than Atom without any files opened (but with a bunch of plugins loaded).
Sorry for the emotional replay, but I just do not understand how people can go from Sublime, which is, in my opinion, almost ideal text editor, to something like this js crap.
since when do you need to edit log files? you don't need an editor for that, you need a log explorer. there are other tools for hat.
what exactly do you mean with proxy problems? i'm behind a proxy at work and didn't have any problems?
> Not to mention the speed and ram usage
that thats its only real problem. especially if you're on a laptop without a power outlet nearby. i tend to just use vim in that situation notice a significant increase in battery life.
> I just do not understand how people can go from Sublime [...] to something like this js crap.
at least its fully extensible. i love the linting, auto-beautification, Markdown Preview, extensible autocompletion, useful autosave, Git-WIP support, extensive git integration and so much more.
its just not meant to be used as anything beside editing small code files. and most people don't have to code monolithic code files beyond a few MB in size.
Any time I want to re-hydrate escaped control sequences like newlines, or explore the log using a host of tools available in a text editor.
> at least its fully extensible
As are most text editors and IDEs. Atom's only difference here is that the extensions must be written in Javascript. Not everyone sees this as a good thing.
> its just not meant to be used as anything beside editing small code files
And that's the problem. Why should a user be forced ahead of time to consider their usecase for editing a file just to choose which gimped file editor they want to use?
No, it's more like having a car that doesn't get to 70mph.
It's useless on the Interstate, and it's also not that good on regular city traffic, because the same limitations that make it unable to reach 70mph also make it clunky at 10mph.
As to why I'm opening such large files: It's not like I chose to do so, but sometimes I have to. It's great to be able to (in Sublime) `<Ctrl+P> log <Ctrl+F> blah` and see immediately what I'm looking for without switching to another tool. I even have a simple syntax highlighting definition for my log file that makes it really nice.
I'd really like to like Atom, but the fundamental problem is that it tries to emulate a text editor widget in a web browser. That works, but creates a certain amount of latency that I can't work with. It's really irritating.
Let me know when they start advertising atom as a source code editor instead of a text editor.
It takes all of 200ms and a wee bit of inference to figure out that their usage of "text editor" is different from yours.
From the tone of some of these posts, you'd think downloading Atom and subsequently realizing it doesn't suit one's needs caused lasting psychological harm.
Semantics aside, Atom is good at what it does. For 99% of projects it's an excellent, flexible tool.
Well, this is simply a bullshit, sorry. This is might be a point of view of someone who never worked on an enterprise project or something of a similar scale.
Atom is good at one thing - opening small js\ruby\python scripts and showing you them in a modern UI. That's it. Anything more than that - he just can't do it.
No lasting harm, but I did invest quite a bit of time to discover that it doesn't suite my needs.
> It takes all of 200ms and a wee bit of inference to figure out that their usage of "text editor" is different from yours.
No it doesn't, it takes experience with the editor. 200ms of googling shows there are some log and tail plugins, which would lead me ot believe it was good at handling large files.
i mean we're talking about opening a file that is 1% of typical system memory.
tail -f *Going through log files and developing software are related, but distinct enterprises. It's no wonder the tools for one are sometimes suboptimal for the other.
Atom is about nice aesthetics, github integration and a plugin ecosystem. It's not trying to solve the problem of reading through massive log files.
Same goes for Sublime. And arguably - Sublime has much better plugin ecosystem. With easier discovery and installation.
I came to Atom from Sublime because the plugin ecosystem was growing much faster and the community felt more active. I haven't looked back since.
And no, Atom not designed to open 30Mb files. Complaining about this is akin to stomping on a land mine and complaining that your Timberland boots didn't save your foot. Just use Atom for its intended purpose: editing source files written by reasonably reasonable people.