Atom 1.33

#1

Post by l2dy » Fri, Nov 30, 2018, 9:53 AM UTC

Atom 1.33
blog.atom.io

Re: Atom 1.33

#2

Post by marsrover » Fri, Nov 30, 2018, 5:00 PM UTC

I'll admit that I haven't used Atom in a very long time, but to be it just seems like a worse version of VS Code.

I don't think I've ever introduced an Atom user to VS Code and they stick with Atom. Every one of them switches.

Re: Atom 1.33

#3

Post by Beefin » Fri, Nov 30, 2018, 5:03 PM UTC

I like the flexibility and customization of Atom but god damn they need to get off the RAM-hogging process that is Electron...

Re: Atom 1.33

#4

Post by benbristow » Fri, Nov 30, 2018, 5:05 PM UTC

Beefin wrote: post #3

I like the flexibility and customization of Atom but god damn they need to get off the RAM-hogging process that is Electron...

Electron is what makes Atom, Atom.

VS Code still uses Electron and that's pretty snappy.

Re: Atom 1.33

#5

Post by cribbles » Fri, Nov 30, 2018, 5:07 PM UTC

I use Atom daily for work, and I am overall satisfied with the editor and its ecosystem, in particular the mammoth improvements the core team has made toward addressing speed issues that plagued the editor in prior years. I haven't tried the new GitHub integration features in this package, but they seem cool.

That having been said - Atom devs, if you're reading this, _please_ put a priority on fixing the auto-update / 'Restart and Install' feature on macOS.[1] If it's not fixable, please remove the option and offer a workaround.

It's gotten to the point where I now simply download the Atom update in browser and manually replace the package binary in my Applications folder, knowing the auto-update will fail.

[1] https://github.com/atom/atom/issues/2860

Re: Atom 1.33

#6

Post by superdaniel » Fri, Nov 30, 2018, 5:10 PM UTC

cribbles wrote: post #5

I use Atom daily for work, and I am overall satisfied with the editor and its ecosystem, in particular the mammoth improvements the core team has made toward addressing speed issues that plagued the editor in prior years. I haven't tried the new GitHub integration features in this package, but they seem cool. That having been said - Atom devs, if you're reading this, _please_ put a priority on fixing the auto-update…

Agreed. It always takes me several tries to update using the "Restart and Install" button.

Re: Atom 1.33

#7

Post by melling » Fri, Nov 30, 2018, 5:14 PM UTC

Beefin wrote: post #3

I like the flexibility and customization of Atom but god damn they need to get off the RAM-hogging process that is Electron...

People complained about Emacs memory usage for decades. Then one day 8 MB wasn’t a lot of memory.

Everyone knows Atom uses a lot of memory. At some point in the very near future, it will no longer be important.

My five-year-old Mac has 16 gigs of RAM. I won’t buy another that has less than 32 gigs.

Re: Atom 1.33

#8

Post by tbirrell » Fri, Nov 30, 2018, 5:16 PM UTC

Does Atom work with mounted directories yet? Especially sshfs? I'd love to go back to Atom, but unfortunately, last time I tried to use it, it had massive indexing problems when working through mounts.

Re: Atom 1.33

#9

Post by dman » Fri, Nov 30, 2018, 5:19 PM UTC

melling wrote: post #7

Beefin wrote: post #3

I like the flexibility and customization of Atom but god damn they need to get off the RAM-hogging process that is Electron...

People complained about Emacs memory usage for decades. Then one day 8 MB wasn’t a lot of memory. Everyone knows Atom uses a lot of memory. At some point in the very near future, it will no longer be important. My five-year-old Mac has 16 gigs of RAM. I won’t buy another that has less than 32 gigs.

This can go the other way too => People kept complaining about Internet Explorer for years. Then one day better alternatives showed up (Firefox, Chrome) and dealing with sub-par experiences was no longer a necessity.

Re: Atom 1.33

#10

Post by rimunroe » Fri, Nov 30, 2018, 5:25 PM UTC

marsrover wrote: post #2

I'll admit that I haven't used Atom in a very long time, but to be it just seems like a worse version of VS Code. I don't think I've ever introduced an Atom user to VS Code and they stick with Atom. Every one of them switches.

Hi. I've been using VS Code for a bit now but I'm actually going back to Atom.

I run into a lot more bugs with VS Code--or at least the (very few) plugins I'm using with it--than with Atom. For example When writing JSX, I'll occasionally add a wrapping element around another, and suddenly I'll get lint warnings about unexpected tokens. Using the "reload window" command or exiting and opening the editor again makes it work, but otherwise I can't get the error to go away.

I also find it to be far noisier by default than Atom. There are so many things on the screen at any given time. The side nav has a bunch of icons, the sidebar seems weirdly un-compact, and it keeps trying to suggest code snippet completions for me. It also seems conventional for VS Code plugins to add inline indicators to the editable region to show things like failing tests or previews of CSS colors. I find things shifting around suddenly on the screen visually jarring, and it makes moving the caret around feel weird. Some of these things are fixable via options, but I like that Atom doesn't require nearly as much fiddling in order to get it to quiet down.

Also, it's slightly annoying to have to reload the editor after installing/removing/disabling/enabling a plugin.