71–80 of 459 posts
I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.
I agree it's a pity.
EDIT: the blog post mentions support for Babel! http://blog.atom.io/2015/02/04/built-in-6to5.html
Congrats! I started using Atom a year ago, but at that time it was very unstable and the performance sucks so I switched back to Vim. This 1.0 still has something to pine for: some of the essential packages are still not updated for the 1.0 API (vim-mode, etc), and when processing large files it still slows down significantly, but as they say, it's now a good foundation to build upon.
If you ever did any development on packages, you may have a development version laying around preempting things. Check in ~/.atom/dev/packages and remove old versions (or git pull them up to the latest dev version).
I had a super old version of tree-view for a long time this way. :)
Is it still limited to only editing files < 2 Megabytes? For most people that is not a showstopper, but it may be for some.
No, recent patch increased the limit to blazing 4 MEGABYTES!
I made the switch yesterday not knowing 1.0 would be released today, and I am seriously psyched. Their Vim bindings are now good enough, and there are tons of tweaks you can do to make them better (which will inspire more people to contribute). I found a few bugs here and there related to installing / removing packages (just checked and 1.0 fixes them), but nothing major, and was able to migrate my mammoth .vimrc con…
what's up with name reuse these days. atom (the syndication format) may be on the verge of becoming obsolete, but it's also forgotten and irrelevant already to warrant a name reuse?
A lot of people complain about the slowness of the Dom/JavaScript backend, but I see a lot of potential for some really cool things, like integrated juPyter notebooks, semi wysiwyg rendering of latex and markdown and maybe drawing rendering trees or other creative things.
I still haven't given Atom a go. Is it worth switching from ST3?
Comes down to preference. I still use sublime for opening really large files. But otherwise i stick with Atom. I've found when using linters, typescript compile checking and such Atom is just better. The notifications built in and such are great, where as the bottom bar for listing that kind of stuff in sublime feels archaic.
(I've held off upgrading because I've always been in the middle of a project... but I'm now realising that I really am just always in the middle of a project, so I might as well just get it over with.)
The killer feature of Atom to me is the ease with which it can be extended (via packages) and the openness to community contribution on core features. That's not a knock against any other editor (some of which share similar characteristics in this regard) – it's just what draws me to Atom. It's super easy to hack on and contribute to.
It's the Cycle of Bloat. 1. Develop tool. It's small and fast and minimal! Woo! 2. It's easy to modify because it's so small! Woo! 3. Look, there's a budding ecosystem of packages! Woo! (Let's not talk about the fact the packages exist precisely because the original product wasn't big enough.) 4. Oh dear, some of them conflict, a lot of them suck. Well, here's some winners, let's pull them into the core. Now the base…
what's up with name reuse these days. atom (the syndication format) may be on the verge of becoming obsolete, but it's also forgotten and irrelevant already to warrant a name reuse?
Is anyone really going to be confusing a text editor and an outdated rss format