Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atom text editor 1.7.0 released

github.com

Post reply on HN
Print view View original

21–30 of 144 posts

Re: Atom text editor 1.7.0 released

#21

Post by davej »

grayrest wrote: post #15
kennywinker wrote: post #9

I've been using Visual Studio Code a bit this past month and there is a lot I like about it. Anyone have thoughts on Code vs Atom? I know Code is based on Atom, but I'm not really clear on how they differ edit: correction. After asking this, I read up a bit and Code is based on Electron which is the core of Atom, but they're fairly different after that.. Code is not a fork of Atom as I thought it was.

Code is not based on atom, it's based on Electron, which is the runtime (node+webkit without the UI chrome). VSCode has lower typing latency and a more considered system for building / debugging / code completion. Atom has a richer plugin api and has been around longer so it has more plugins. I've done basic plugins for both and plan on using/developing for VSCode but I've been too lazy to write Vim bindings and not…

Nitpick, Electron is Node + Chromium (not webkit).

Re: Atom text editor 1.7.0 released

#23

Post by Couto »

spdustin wrote: post #18
juli3n wrote: post #16

Earlier quoted context omitted.

Yep, but you can disable it by disabling the 'metrics' extension.

That's _after_ the first launch, correct?

Not necessarily. You can set the property in your ~/.atom/config.cson before the first run.

https://github.com/Couto/.dotfiles/blob/master/tag-atom/atom... in case you need an example

Re: Atom text editor 1.7.0 released

#24

Post by ShrpErinaceidae »

cortesi wrote: post #17
nickpeterson wrote: post #3

Doesn't indicate perf improvements... Not trying to troll, but that surprises me given the large number of complaints about performance.

I'm making a bit of a habit of chipping in on Atom performance complaints with a counterpoint. I've now used Atom as my primary editor for more than a year, and I have no complaints about the performance. This could be because I'm using OSX on recent hardware - I've noticed that my friends using Linux desktops seem to have more issues than I do.

Having both Atom and VS Code installed on recent hardware I can say VS Code definitely feels snappier in multiple aspects. It's hard to believe both editors share Electron roots.

And not to make this an X is better than Y comment, but the much better (in my experience) high-DPI handling with VS Code does the same. I wonder what exactly VS Code does to manage to be the only Electron based application that I've used that scales properly across multiple monitors at different DPIs.

Re: Atom text editor 1.7.0 released

#25

Post by ShrpErinaceidae »

cortesi wrote: post #17
nickpeterson wrote: post #3

Doesn't indicate perf improvements... Not trying to troll, but that surprises me given the large number of complaints about performance.

I'm making a bit of a habit of chipping in on Atom performance complaints with a counterpoint. I've now used Atom as my primary editor for more than a year, and I have no complaints about the performance. This could be because I'm using OSX on recent hardware - I've noticed that my friends using Linux desktops seem to have more issues than I do.

Having both Atom and VS Code installed on recent hardware I can say VS Code definitely feels snappier in multiple aspects. It's hard to believe both editors share Electron roots.

And not to make this an X is better than Y comment, but the much better (in my experience) high-DPI handling with VS Code does the same. I wonder what exactly VS Code does to manage to be the only Electron based application that I've used that scales properly across multiple monitors at different DPIs.

Re: Atom text editor 1.7.0 released

#26

Post by maxehnert »

They hijacked the way you open files now and from what I can see reading through release notes and commits there's no way of opening a file permanently without double clicking.

With preview mode enabled I have to dbl click the tab and with it disabled I have to dbl click the file name. It would be nice if opening a file had regular single click functionality when preview mode was disabled. Or maybe another setting for this in the config.cson file.

It seems like a trivial thing to complain about but it's usually the small things like this that are the most annoying (for me at least).

Re: Atom text editor 1.7.0 released

#27

Post by melling »

llamataboot wrote: post #4
nickpeterson wrote: post #3

Doesn't indicate perf improvements... Not trying to troll, but that surprises me given the large number of complaints about performance.

Yeah, Atom is really my favorite editor at the moment in terms of features and add-ons but is totally unusable for me due to various performance issues. Not only does it choke on large files but something like a full-project search can take upwards of 30s to finish while Sublime Text finishes it in about 2-3s. I'd like to switch personally, but I can't until some major performance improvements happen. YMMV.

Unless you tell someone your OS and hardware, it's really not helpful for people to decide, or even address the problems.

Does Atom use a lot of ram or cpu? I've got a 2 year old Mac Book Pro with 16 GB RAM and an SSD. I downloaded Atom 1.6 after the announcement and leave it open to maintain my notes and I haven't noticed any performance problems with a couple dozen files. I might try to use it for another project once I evaluate the plugins.

Re: Atom text editor 1.7.0 released

#30

Post by rayiner »

santaclaus wrote: post #7
nickpeterson wrote: post #3

Doesn't indicate perf improvements... Not trying to troll, but that surprises me given the large number of complaints about performance.

The performance problems on a clean Atom install are incredibly vexing. Microsoft's Visual Studio Code is built on similar foundations and has great performance, so I don't think Atom's performance problems are fundamental.

Visual Studio Code is a totally different foundation. The only shared piece is the Electron shell for embedding Chrome.
Post reply on HN