Live data from Hacker News

Atom 1.0

blog.atom.io

321–330 of 459 posts

Re: Atom 1.0

#321

Wow... just downloaded the windows installer version and it autoinstalled itself wherever it chose fit, without questioning, it installed shortcuts on the start menu, placed itself on an already bloated contextual menu on several file extensions as an Open option, instead on "Open with...", etc. I usually install software on my user folder on the work laptop, as I don't have enough priviledges. This time the installe…

I clicked the download button and noticed 70+ MB file. I thought to myself, why in the world a text editor needs to be so huge. And then I see your comment. I clicked on the Pause button on my download.

Did you intend to run it in a potato? Even a raspberry pi would have no difficulty with that file size.

It's also packing a full browser, don't forget that. And likely all sorts of assets.

I particularly don't care. I'm more interested in how it performs during use.

By the way, task manager indicates it's using less then half that of RAM, with a few tabs open.

Re: Atom 1.0

#322
post #310

Earlier quoted context omitted.

Do you really want to open log files in a code editor? It's not unreasonable to say that these are two different classes of programs, with different basic requirements.

I've been opening log files in either vi, notepad++, or sublime text for as long as I can remember. I've never had any issues accomplishing exactly what I needed. You insinuate that's a bad thing without providing any examples or solutions that are "better", so I can only assume your rationale is: My tool is awesome even though it doesn't fit your requirements, so you should change your requirements.

I definitely don't mean to insinuate it's a bad thing, but for me it is not a core requirement. Atom is supposed to be a code editor, and it's no hardship to use a different program for opening non-code text files. I actually find native text editors (I've tried Scratch and Gedit) don't work better than Atom for largish text files of a megabyte or thereabouts, so it's clearly a relatively common issue with editors which are built on the assumption you're going to be looking at smaller files. If the Atom devs manage to write the code which will allow these files to be handled, great, but in the meantime the program remains excellent for editing code.

Re: Atom 1.0

#323
post #74

Earlier quoted context omitted.

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.

My Emacs with all customizations takes longer than Atom does to startup.

Which, for Emacs, is not an issue at all. Leave the server running and all clients will open instantly whenever I ask.

Re: Atom 1.0

#324

Earlier quoted context omitted.

I don't know if this has changed, but when I tried Atom and didn't like it, I discovered that there was no uninstaller. Hooray for deleting context menu entries by hand in the registry.

One of the first things I've noticed after trying out the new release, very annoying.

Thanks for the heads up, I was about to try Atom but I'll wait until this is fixed.

Re: Atom 1.0

#325
post #238

Earlier quoted context omitted.

You can call CoffeeScript functions from JavaScript and vice versa. There's no reason that you can't use the UI library from code written in JS. The fact that its written in CoffeeScript is an implementation detail

But all the docs are in Coffeescript, and it's quite hostile to a new dev.

Grab a cup of coffee, start reading the CoffeeScript documentation. Your coffee won't even by cold by the time you finish with it. Start coding.

Seriously, CofeeScript is tiny.

Re: Atom 1.0

#326

Earlier quoted context omitted.

Yeah this is crazy. I regularly work with log files in the 100mb to 300mb range which open perfectly fine in Vim/Sublime. If I had to invest time in learning Atom I'd have to multitask between editors for certain use-cases. Maybe if they could switch to a light-weight read-only type of text "viewer" for large files, that would even work. But I really do need to open big files on a weekly basis.

Do you really want to open log files in a code editor? It's not unreasonable to say that these are two different classes of programs, with different basic requirements.

I find this to be a really tired discussion/response that pops up whenever new software comes around.

"X doesn't do Y" "Did you really want Y"?

Of course they do, they just complained about it.

> It's not unreasonable to say that these are two different classes of programs, with different basic requirements.

But it is reasonable to hold a piece of software up to standards set by the majority of other software in the same realm. Other text editors can open log files, this one probably should be able to, too.

Re: Atom 1.0

#327

Wow... just downloaded the windows installer version and it autoinstalled itself wherever it chose fit, without questioning, it installed shortcuts on the start menu, placed itself on an already bloated contextual menu on several file extensions as an Open option, instead on "Open with...", etc. I usually install software on my user folder on the work laptop, as I don't have enough priviledges. This time the installe…

I don't know if this has changed, but when I tried Atom and didn't like it, I discovered that there was no uninstaller. Hooray for deleting context menu entries by hand in the registry.

I was able to uninstall it from the Programs list and context menu entries are gone.

Re: Atom 1.0

#328
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…

I must say, the same people that criticized Eclipse for its "bloat" that are now making excuses for the bloat in Atom is very amusing.

In terms of performance, stability and extensions this doesn't even hold a candle to Eclipse Mars.

Re: Atom 1.0

#329

Wow... just downloaded the windows installer version and it autoinstalled itself wherever it chose fit, without questioning, it installed shortcuts on the start menu, placed itself on an already bloated contextual menu on several file extensions as an Open option, instead on "Open with...", etc. I usually install software on my user folder on the work laptop, as I don't have enough priviledges. This time the installe…

This frustrates me to no end. I prefer to install my software in a certain location. Having it selected for me is not okay. Nor is giving me the option to override it.

Re: Atom 1.0

#330
post #167
post #79

Earlier quoted context omitted.

How is it outdated? Atom is absolutely everywhere and there's no replacement, or a need for it.

I suppose I meant the concept of RSS or whatever is itself outdated/unused to most people

That might be true for the classic case of following blogposts, but it's used under the hood all over the place. I'd call it one of the few absolute wins in standards on the web. It's ubiquitous for its use-case.
Post reply on HN