Live data from Hacker News

Atom 1.0

blog.atom.io

111–120 of 459 posts

Re: Atom 1.0

#111
post #37

Earlier quoted context omitted.

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

People editing files longer than that are certainly in the minority.

I severely doubt that. You don't edit them every day, but:

1) It comes up sometimes, and your editor should cope 2) Having a hard file size limit so low is (to me) indicative of you doing something wrong.

Re: Atom 1.0

#112
post #98

Earlier quoted context omitted.

That's really only a problem if you're contributing to the core, right? You can write your own packages in JS, and if you're just a user of the editor I don't see how that matters.

Sure, but it's not the same, on one side I'd like to read the core and hack it on my own terms, on the other I'd feel more comfortable writing packages if I could just read the core and see how things work under the hood. I'd like it to be a "hackable editor" as it touts itself, but as it stands right now it's a "hackable editor if you are comfortable with CoffeeScript".

You can write in Plain JS if you want (it supports Babel, apparently); CoffeeScript is not a hard limitation, just a preference.

Re: Atom 1.0

#113
post #74
post #70

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 are the main advantages that atom gives you over native vim?

None.

Atom's installer is a huge download, and the editor is much slower ... It also consumes much more memory and written in coffeescript. Takes a long time to start up ... just a few things on the top of my head.

It's a great initiative though so that's already a good point.

Re: Atom 1.0

#115
Just downloaded and opened Atom for the first time, and I have to admit the look and feel is amazing! Fantastic job to all those involved!

However, one thing that stands out to me, the file size of Atom.app is 203MB!! How in the world can a text editor be that large? Compare that with MacVim, which is about 27MB.

Re: Atom 1.0

#116
post #71
post #56

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

I was a big supporter of their choice of CoffeeScript... until @jashkenas et al decided not to adapt to ES6. Now the language is dead and users are better off migrating to Babel and just dealing with the curly braces and commas. 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

When did @jashkenas decide not to adapt to ES6? I searched and found this, which indicates they're open to it. Someone just needs to implement it.

https://github.com/jashkenas/coffeescript/issues/3162#issuec...

Re: Atom 1.0

#117
post #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.

I'm running Atom 0.116.0 on Xubuntu and AltGr works perfectly fine. My keyboard layout is Norwegian.

Re: Atom 1.0

#118
post #2

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

I only keep using ST because of: https://github.com/atom/atom/issues/5344 https://github.com/atom/fuzzy-finder/issues/57

People just don't seem to know how to do fuzzy searching. Xcode has the same problem. I used Xcode every day for 2 years and its fuzzy matching never once made me happy.

Fortunately, I have a concrete solution: copy what Visual Assist does. Space-separated substrings. It makes it very easy to be more precise about what you're looking for, while still letting you be vague when you'd rather, and the computer never has to make a judgement call.

See here: http://docs.wholetomato.com/default.asp?W193 and search for "filtering in the dialog" (their page has no anchors! - I'm certainly not suggesting you should copy their HTML style)

Re: Atom 1.0

#119
post #86
post #60

Earlier quoted context omitted.

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…

Do people believe that having access to packages and add-ons makes an editor (or whatever else) "bloated and slow"? First, whatever you don't use, it's not even loaded in memory. Second, bloated is all about having tons of options you don't need or use. Not about adding stuff you DO need piecemeal. Third, bloat is mostly a UI thing, not a "number of add-ons" or "too many lines of code" thing. Programs don't get slow…

The parent did not say that plugins caused bloat, instead that resolving common problems with plugins (stability, quality, conflicts etc.) by pulling them into core is what causes bloat (slowness, complexity etc.) and that trying to resolve the tension between flaky plug-in based systems and bloated monolithic systems is cyclical.

Re: Atom 1.0

#120

I find it to be a bit depressing that software bloat has advanced to the point that we have text editors plagued with performance issues.

Thirty years ago people complained that GNU Emacs needed 8 megabytes of RAM.
Post reply on HN