Live data from Hacker News

Atom text editor 1.7.0 released

github.com

41–50 of 144 posts

Re: Atom text editor 1.7.0 released

#41
post #33

Earlier quoted context omitted.

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.

> Microsoft's Visual Studio Code is built on similar foundations This is my understanding of things: - Electron is built on top of Chromium, where the technology was mainly driven by Google and their engineers. - Vscode is based on Monaco which Erich Gamma and his team spear headed. - Atom is based on work done by GitHub. The analogy would be they both use Honda engines, but Microsoft appears to be able to use Honda'…

No this is pretty wrong. They are both built on Electron which is just the window shell hosted in Chrome. The actual text editors are completely different code bases that have nothing to do with each other.

The better analogy would be they are both built using Honda doors, but they each have completely different engines.

Re: Atom text editor 1.7.0 released

#42
post #30

Earlier quoted context omitted.

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.

That's sort of the foundation though right? The editor built into the electron app is completely different, suggesting that atom is theoretically able to achieve similar performance.

I haven't used visual studio code myself, but does it use a mix of JavaScript and HTML to render and process the text? If so then isn't the major differences the algorithm choices for rendering and editing text?

Re: Atom text editor 1.7.0 released

#43

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 fo…

It's in settings. You can disable preview panes. Agree it was annoying.

Re: Atom text editor 1.7.0 released

#44
post #17

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.

It's alright for small files, but whenever I paste in a huge csv or json file it hangs for minutes. And I use pretty recent macbook pro with high specs. This doesn't happen with other editors.

Re: Atom text editor 1.7.0 released

#45
post #29

For you Atom users: Why have you chosen Atom over, say, Emacs?

The handling for modern Javascript development tools is superior than any other editor I've used, Vim and Emacs included unfortunately. I use Vim for everything, except JS development. For that I use Atom.

Re: Atom text editor 1.7.0 released

#46
post #17

Earlier quoted context omitted.

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.

It's alright for small files, but whenever I paste in a huge csv or json file it hangs for minutes. And I use pretty recent macbook pro with high specs. This doesn't happen with other editors.

I've found that when pasting in huge files, disabling syntax highlighting makes a big difference. In fact, if you simply open a sufficiently large (I haven't bothered bisecting the size, but a few megs works) xml file, Atom will disable syntax highlighting by default and the performance will be slow but still usable. If you paste in the contents of a large xml file, syntax highlighting is not disabled and the editor either hangs or crashes, in my experience.

Re: Atom text editor 1.7.0 released

#47
post #27

Earlier quoted context omitted.

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 o…

You shouldn't need a $2000 laptop to run a text editor.

Re: Atom text editor 1.7.0 released

#48

You know what I would really enjoy? Being able to sign into your Github account and sync your preferences and packages to the cloud. Then if I sign in on a different computer, all my hotkeys, packages and themes are copied over seamlessly. As a crappy workaround I have this: https://github.com/sergiotapia/atom-meteor-packages But still, I would like this to be a core integration. I've since switched to RubyMine and W…

Agreed that this should be built in. I've been using https://github.com/atom-community/sync-settings which stores everything in a gist and has worked out reasonably well so far. The pain points are that you have to manually set it up the first time with the gist id and (optional) private api key, and backups have to be triggered manually.

Re: Atom text editor 1.7.0 released

#50

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…

You may want to try my vim extension for VSCode - amVim. It works best on VSCode's insiders build now. I'm planning a big update as soon as VSCode releases 1.0(which is said to be 4/14)
Post reply on HN