Live data from Hacker News

Atom was archived today

github.com

41–50 of 614 posts

Re: Atom was archived today

#42
post #32
post #7

Sad to see this go. I was an early adopter of Atom, and I wrote two extensions for it, one of which while it was still in beta. The Atom developers made some technology choices that in retrospect were ill-advised, CoffeeScript being the worst of them and splitting everything into dozens of packages a close second. They tried to backpedal on both of these later on, but by that time VSCode, with its far superior engine…

Atom predated the LSP and leaned heavily into customizations with all the plugins running inside the UI thread (more like a traditional web page and 3p scripts). At the time they viewed the extreme customization support as a feature, and there was a thriving ecosystem of folks making plugins. That architecture has a major flaw though. A default install was fast, but a real configuration with all the plugins ended up…

[deleted]

Re: Atom was archived today

#44
post #11
post #7

Sad to see this go. I was an early adopter of Atom, and I wrote two extensions for it, one of which while it was still in beta. The Atom developers made some technology choices that in retrospect were ill-advised, CoffeeScript being the worst of them and splitting everything into dozens of packages a close second. They tried to backpedal on both of these later on, but by that time VSCode, with its far superior engine…

People hate on electron, but it's a pretty amazing piece of tech if you ask me. I can turn a browser game into a steam game with basically no effort which is nice because browsers change over time and electron helps you get a working offline snapshot of something you created.

> I can turn a browser game into a steam game with basically no effort

There's actually quite a lot of effort required if you want Steam overlay to work and/or not crash with Electron, or to interact with Steamworks APIs.

Re: Atom was archived today

#45
post #37
post #18

Earlier quoted context omitted.

Electron is essentially an operating system that runs on every operating system, so you can target just a single OS and your application works everywhere.

Yes, and that's exactly what people hate about it: every application written in Electron lugs around its own copy of this OS. You can imagine why this might not be a good idea, especially for applications designed to run in the background, like the Slack client. For me, it was a godsend when Slack decided that my Linux version was too old to support and the client stopped working. Then I switched to the in-browser ve…

I strictly run Teams, Slack, Discord, and Spotify in pinned browser tabs

Re: Atom was archived today

#48
post #9

Earlier quoted context omitted.

emacs may probably let you do this too, and better. The big problem is: You need to know emacs beforehand, which is seriously a lot, and likely bizarre to any modern person. I do, and I will likely never give it up, but I've been at it since the 90s. In my mind, emacs suffers the same problem as TeX/LaTeX. Some parts of it are very antiquated and just don't fit into the modern world anymore. They'd need an overhaul.…

Then the joke evolved to that it couldn't open files 8MB or larger without hanging, at one point.

Yeah. I did feel the original joke, though. There's a reason why emacs had this weird "unexec" bootstrap during building that would run emacs, compile all its lisp, and just dump all its memory back onto disk to be the actual executable.

My first Linux PC had 8MB RAM, long long after emacs became a thing. If emacs' resident set came even close to half of that or so, "constantly swapping" would have been reality.

Re: Atom was archived today

#50
post #36

Make no mistake... This project, Atom. Provided the runway that others copied, then improved upon (and on and on... with plenty of funding). Atom provided the seed, excitement and vision for what is possible on this platform, and should be proud of that fact.

That is how we all will remember Atom.
Post reply on HN