Live data from Hacker News

Sunsetting Atom

github.blog

561–570 of 880 posts

Re: Sunsetting Atom

#561

Founder of Atom here. We're building the spiritual successor to Atom over at https://zed.dev . We learned a lot with Atom and had a great time, but it always fell short of our vision. With Zed we're going to get it right. Written in Rust, custom native UI framework, engineered to be collaborative. Just starting our private alpha this week, so the timing of this announcement feels quite fitting. Here's a talk I gave l…

Hey,

Please don't forget about accessibility. Getting this right from day 1 will make your life a lot easier in the long run. If I remember correctly, I was never able to use Atom with a screen reader. Hearing custom UI already makes me nervous and I'm pretty sure I won't be able to use Zed with a screen reader either.

Blind developers exist. Please don't forget about us. It's one of the few areas where we can actually make a meaningful difference together with our peers on an equal playing field.

Re: Sunsetting Atom

#562

I held out for a year or so after VSCode was released. It felt scummy how MS had swooped in and tried to hijack this new category of editor that GitHub had invented (this was before they'd been acquired, I believe) But once I tried VSCode... man, there was no going back. It was infinitely more performant and cohesive. Atom (with IDE-like features installed) felt so sluggish by comparison. I think the main improvement…

> Atom extensions could have dependencies on each other This. This always has been and always will be a critical ecosystem mistake. The principle of one msi/exe installing everything you need on Windows, one click downloading an entire app from a store on Android or iOS is seamless and almost always error free. Or in your example with VSCode having self contained encapsulated plugins that install with one click. Mean…

That seems extreme.

Any ecosystem has to strike a balance between which things should be opinionated/officially-sanctioned/standardized, and which things should be left open in "userspace". I think Atom made the wrong choice by outsourcing some very standard features to the community, like hover-overs and underlines. VSCode seems to have hit a sweet-spot, offering standard solutions for common functionality but leaving plenty of doors still open for people to build on.

Re: Sunsetting Atom

#563

Earlier quoted context omitted.

Interesting! I just wanted to let you know my perspective, which is probably quite unique. I started using atom pre-1.0, a long, long time ago. I immediately jumped to vscode when I realised it existed. The reason is a bit weird; it's the find-in-files/project (c-s-F/Ctrl+Shift+F) sidebar search/replace feature. Compared to the Atom (and from what I can see in the youtube talk, zed has the same "problem") which opens…

> I code mostly in domain-specific, esoteric, private languages, no stdlib or docs, and no online resources to learn from. Jesus, who are you?

A brainfuck developer?

Re: Sunsetting Atom

#564
post #549

I held out for a year or so after VSCode was released. It felt scummy how MS had swooped in and tried to hijack this new category of editor that GitHub had invented (this was before they'd been acquired, I believe) But once I tried VSCode... man, there was no going back. It was infinitely more performant and cohesive. Atom (with IDE-like features installed) felt so sluggish by comparison. I think the main improvement…

> It invented the entire concept of web apps as desktop apps Mozilla actually had that in early 2000 or so; their whole UI (before Firefox existed, even) was a webby. Except it was their own weird sort of webby and not normal HTML, most of the time. Using normal HTML would be around IE4 with their .hta files, I think. Didn't seem to have too much uptake though.

Fair! Maybe I should've said "got web apps as desktop apps to finally take off"

Re: Sunsetting Atom

#565

I held out for a year or so after VSCode was released. It felt scummy how MS had swooped in and tried to hijack this new category of editor that GitHub had invented (this was before they'd been acquired, I believe) But once I tried VSCode... man, there was no going back. It was infinitely more performant and cohesive. Atom (with IDE-like features installed) felt so sluggish by comparison. I think the main improvement…

> It felt scummy how MS had swooped in and tried to hijack this new category of editor that GitHub had invented Wasn't brackets and atom released pretty much at the same time, both built on CEF?

Interesting! I hadn't heard of brackets before.

Re: Sunsetting Atom

#566

Earlier quoted context omitted.

Interesting! I just wanted to let you know my perspective, which is probably quite unique. I started using atom pre-1.0, a long, long time ago. I immediately jumped to vscode when I realised it existed. The reason is a bit weird; it's the find-in-files/project (c-s-F/Ctrl+Shift+F) sidebar search/replace feature. Compared to the Atom (and from what I can see in the youtube talk, zed has the same "problem") which opens…

> I code mostly in domain-specific, esoteric, private languages, no stdlib or docs, and no online resources to learn from. Jesus, who are you?

Retired? Or in Academia?

Re: Sunsetting Atom

#567
post #165
post #2

It's what kickstarted Electron which eventually gave us VSCode, Slack, and lots of HN comments about memory usage. It also had the sweetest default theme of any code editor. RIP.

Electron is both an amazing enabling technology, and also an artifact of the sad state of affairs for computing platforms. One could imagine a world where strong standards have been established which would allow you to easily deploy lean native applications across a wide variety of platforms. Instead we ended up in this bizzare world where if you want to maintain a desktop GUI app, you either need a large team to sup…

I'm wondering how viable a for-profit electron replacement (with native support) would be? Like Unity (similar business model), but exclusively thought for apps.

Re: Sunsetting Atom

#568

Earlier quoted context omitted.

Interesting! I just wanted to let you know my perspective, which is probably quite unique. I started using atom pre-1.0, a long, long time ago. I immediately jumped to vscode when I realised it existed. The reason is a bit weird; it's the find-in-files/project (c-s-F/Ctrl+Shift+F) sidebar search/replace feature. Compared to the Atom (and from what I can see in the youtube talk, zed has the same "problem") which opens…

> I code mostly in domain-specific, esoteric, private languages, no stdlib or docs, and no online resources to learn from. Jesus, who are you?

im guessing a very loyal employee to an enterprise company outside of tech - probably logistics

Re: Sunsetting Atom

#569

Earlier quoted context omitted.

Atom practically invented the kind of extensions that VSCode had, and even several years into VSCode's life Atom far outstripped it in Extensions. Perf became the biggest problem however, which VSCode took over.

Sublime, TextMate, …

BBEdit.

Re: Sunsetting Atom

#570

Earlier quoted context omitted.

Interesting! I just wanted to let you know my perspective, which is probably quite unique. I started using atom pre-1.0, a long, long time ago. I immediately jumped to vscode when I realised it existed. The reason is a bit weird; it's the find-in-files/project (c-s-F/Ctrl+Shift+F) sidebar search/replace feature. Compared to the Atom (and from what I can see in the youtube talk, zed has the same "problem") which opens…

> I code mostly in domain-specific, esoteric, private languages, no stdlib or docs, and no online resources to learn from. Jesus, who are you?

DoD?
Post reply on HN