Live data from Hacker News

Atom 1.0

blog.atom.io

51–60 of 459 posts

Re: Atom 1.0

#51

Congrats! I still prefer emacs but perhaps not for long (I use both day to day)...

I use emacs but might try atom when it's a true replacement possibility. How can I know it's crossed the threshold?

Re: Atom 1.0

#53

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.

While I see that as a strength it might be a double edged sword. I installed a few packages I thought were necessary and soon Atom was crashing constantly and was riddled with bugs. I think it's possible that too many people have the ability to control core pieces of what makes Atom so good and as a result the experience degrades.

Re: Atom 1.0

#54
post #51

Congrats! I still prefer emacs but perhaps not for long (I use both day to day)...

I use emacs but might try atom when it's a true replacement possibility. How can I know it's crossed the threshold?

I'm really looking forward to emacs-like tab behavior and also now that the rate of change will slow down we'll likely see the best quality extensions rise to the top and stabilize a bit.

Also looking forward to seeing Facebook's fork of Atom for React...

Re: Atom 1.0

#55
Eh. Why is 1.0 out already? Keyboard layouts which use AltGr are still broken.

E.g. I can't type '@', '\', and 'µ'. Yes, I can't write metadata annotations or escape some characters.

Re: Atom 1.0

#56
I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.

Re: Atom 1.0

#57
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.

Re: Atom 1.0

#58

Earlier quoted context omitted.

No, recent patch increased the limit to blazing 4 MEGABYTES!

Without code highlighting though, if I remember correctly. I don't see myself editing a >2MB file containing code, but still...

how about something like sqlite3?

https://www.sqlite.org/download.html

shows the amalgamation, which is the main thing you'd build, having a 5.4 MB sqlite3.c file. I can easily see someone making a change to it if they wanted slightly different behavior - or to consult it for canonical behavior - and I was pleased I could glance through it in Sublime.

Re: Atom 1.0

#59
post #21
post #2

I still haven't given Atom a go. Is it worth switching from ST3?

I would say that it's at 90+ percent feature parity with ST3; the only real downside is that the package/extension ecosystem is nowhere near as mature as with ST3 right now, but that looks like it is changing very quickly. In addition, ST3 is closed source vs. Atom is open source, and that alone could be a good reason for a number of people to switch. My recommendation is to give Atom a chance, see if it fits into yo…

the package ecosystem isn't on par yet, but the package DEVELOPMENT ecosystem far surpasses sublime in every way imaginable.

I really did not enjoy writing plugins for sublime. The development/debugging/testing experience isn't especially pleasant.

Re: Atom 1.0

#60

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 system is that much better! Woo!
    5. Repeat 3 and 4 a few times.
    6. Crap, this tool is all bloated and slow. I'm going to go
       create a small, fast, minimalist solution!
Repeat indefinitely.

See also: "minimalist web framework", "minimalist Linux distribution", "minimalist programming language".

Post reply on HN