Live data from Hacker News

Atom 1.33

blog.atom.io

11–20 of 55 posts

Re: Atom 1.33

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

I use a Mac and I've never had that issue; strange :/

Re: Atom 1.33

#12
Anyone know what light ui/theme they are using in the demo/screenshots here? Is it simply the packaged atom light theme? It looks beautiful.

Re: Atom 1.33

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

"eight megs and constantly swapping"

Re: Atom 1.33

#14
post #12

Anyone know what light ui/theme they are using in the demo/screenshots here? Is it simply the packaged atom light theme? It looks beautiful.

At the risk of heresy, I agree. It looks really clean and appealing.

Re: Atom 1.33

#15
post #9
post #7

Earlier quoted context omitted.

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.

People complained about the lack of functionality in IE. Atom is functional and iterating fast.

It works great on my 5 year old Mac Book Pro with 16 GB. I understand that some people do have more minimal hardware, but 16GB looks like a $100 investment. Performance and memory usage are being addressed.

I simply see memory usage as less of a problem in 2018/2019. I want more functionality.

Re: Atom 1.33

#16

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.

Same. With VSCode most plugins "just work" as I expect them too, and it's also usable with 0 plugins.

Atom plugins otoh... they're a s-fest of stuff requiring other stuff and never managing to ever auto-magically just work. For Python and JS VSCode is amazing! Also there's a Jupyter plugin that works, an integrated terminal that just works, making it idea for data-science and ML tasks too...

I have no idea what the Atom guys are doing, because in theory I'd like Atom more, but in practice I fee like wanting to throw my laptop at a wall after 30 min of using it because of how semi-broken everything is.

Does anyone anyone have a "curated" set of Atom configs and plugins that "just work"? Maybe by making it into smth like "a distro", it could be usable for people with 0-to-little-patience like myself...

Re: Atom 1.33

#18

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.

IntelliSense. Definitely my reason for not going back.

Re: Atom 1.33

#19

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.

After looking at both, I chose Atom.

The VS Code developers observed that things can pretty tangled with open-ended plugins and HTML rendering, so they cordon off plugins to separate processes, and only offer limited UI control to plugins. This helps keep things stable and fast, but I think the ability to have plugins easily create new UI in an open-ended way is the coolest feature that Electron enables in an editor.

Atom offers a lot more UI control to plugins, and in my experience, is still acceptably fast and stable.

Re: Atom 1.33

#20
I wish they could get Ruby working in Atom out of the box. I still can‘t believe how weak the tooling is in the Ruby on Rails world. Even Jetbrains fails miserably. Why on earth can‘t we have decent code completion in Ruby?! If the human brain can tell what will be available why can’t my computer.
Post reply on HN