Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sunsetting Atom

github.blog

Post reply on HN
Print view View original

281–290 of 880 posts

Re: Sunsetting Atom

#281

Post by Santosh83 »

keewee7 wrote: post #79

Really begs the question what Visual Studio Code did right and what Atom did wrong.

MS poured developers at VS Code which resulted in it blowing away Atom pretty soon in terms of performance. Soon devs started migrating to VSC, plugin ecosystem started accreting, and gradually people just forgot about Atom. It is not that Atom did anything horrendously wrong. If the same dev effort had been put into it that VSC got, am pretty sure it could've become almost as good now. Maybe even better in certain respects.

Re: Sunsetting Atom

#284

Post by mikewhy »

lmarcos wrote: post #187
joshstrange wrote: post #56

I know a lot of people love vscode but are there any people who have tried something like IDEA/WebStorm/PHPStorm/etc that then went back to vscode? I had to help a developer setup deploys to a dev server from vscode the other day and I wanted to pull my hair out. I'll admit it's at least in part due to not using vscode myself but I was a heavy Sublime Text user which is very similar to vscode when it comes to how you…

I cannot stand the "dancing" sidebar in VS Code. It's used for showing the directory tree, search results, plugins, etc. I like Jetbrain IDEs (at least on my machine they load and feel fast).

FYI you can drag anything from the sidebar to the bottom pane. It's not much, but can help with the overloaded sidebar.

Re: Sunsetting Atom

#285

Post by 420official »

nathansobo wrote: post #253

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…

What's the reasoning behind this iteration being closed-source?

Re: Sunsetting Atom

#286

Post by quaunaut »

aniforprez wrote: post #277
nathansobo wrote: post #253

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…

IMO the killer thing that VSCode has over all the other editors is the wealth of extensions and a certain degree of simplicity. What are your plans for Zed in terms of extensibility and are you aligning more towards making something beefy and full-featured like the IntelliJ offerings or something more "lightweight" like VSCode or Sublime?

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.

Re: Sunsetting Atom

#287

Post by xbar »

mumblemumble wrote: post #47
Doctor_Fegg wrote: post #7

“Sunsetting” an open source project seems… unfitting? Hand it off to the community, look for new maintainers, donate it to the Apache Retirement Home for Veteran Projects, sure. But saying that you’ve decided to “sunset” or “archive” it, telling users to plan for their migration, seems counter to the notion that open source software forms part of a commons - something that Github, of all companies, should understand.

The code isn't being sunsetted, and anyone who wants to take it and keep working on it is free to do so. But winding down the project is still a major event, and I think that it is appropriate to call that sunsetting. The existing project organization will go away. The team will presumably dissolve, with any people being paid to work on it going on to other things. I've seen this happen enough times to know that it i…

Precisely.

This is a responsible way to handle the ceasing of maintenance while allowing any and all interested members of the Atom community to fork and maintain versions.

I have a much more optimistic view of development communities than you do, and I expect to see Atom endure in some forms.

Re: Sunsetting Atom

#288

Post by jlkuester7 »

bellBivDinesh wrote: post #141

Atom was my first go to editor years ago when its git integration felt miles ahead. Then I saw gitglass(?) in VS Code and was moved to switch for shared workspace files at my job. I remember it as lightweight and fun.

I have never found a git integration that I liked more or found more simple and intuitive than Atom's. I found that even folks who were new to git would quickly become comfortable with managing git interactions via Atom.

VSCode's "Source Control" on the other hand is a such a big UX dumpster-fire that I cannot bring myself to even try using it any more....

Re: Sunsetting Atom

#289

Post by onionisafruit »

alxlaz wrote: post #131
civilized wrote: post #14

Earlier quoted context omitted.

GitHub is owned by Microsoft, the company that invented "Embrace, Extend, Extinguish". We should be counting down the days till they sunset VS Code to focus on VS Code "Pro".

VS Code "Pro" is very 1998. My money is on VS Code 365.

It’s already here. They went with the name GitHub Codespaces.

Re: Sunsetting Atom

#290

Post by bckr »

speedgoose wrote: post #222
joshstrange wrote: post #160

Earlier quoted context omitted.

On save, deploy the file out to a dev server(s) that runs the full stack (1 or more server per developer that only they use).

It sounds like your development flow is a bit unusual nowadays, which could explain why no one bothers to maintain such vscode plugin.

I have to agree. I'd rather open the terminal and do a git push or otherwise run a command rather than having every save get deployed.
Post reply on HN