Live data from Hacker News

Sunsetting Atom

github.blog

631–640 of 880 posts

Re: Sunsetting Atom

#631

Earlier quoted context omitted.

Humble question, I don't mean to sound confrontational, I ask of genuine curiosity: Why not contribute to VS Code instead? For Julia, Atom+Juno was excellent. It was the first time I could select+run on a proper IDE (I was coming from python+notebook). To me this was revolutionary. Then I discovered VS Code, so Atom+Juno stopped making sense. You seem to be a very competent developer, so why not just contribute to VS…

I don't think VS code would ever accept a change to native UI or switch off of electron, so it seems like a nonstarter for someone who wants to experiment with native UI text editors. VS code is written almost 100% in JS and typescript, it will always be a nodejs app through and through without a complete rewrite. And even if they wanted to rearchitect VS code all of the extension APIs, extensions themselves, etc. wo…

you don't need node.js/V8 for plugins

there is quickjs and some others, some of them are rust-based and all of them can run in wasm host

EDIT: to be honest, I clearly see where you are going with this and I agree :)

Re: Sunsetting Atom

#632

Earlier quoted context omitted.

I’m not sure the term has ever been applied to Microsoft’s own products…

Atom was developed before the acquisition. Which brings us to the second proud tradition of the tech titans, acquiring companies to end the products the acquirer doesn't like.

it was dead already, or at least, shown inferior to vscode in feature set. If anything you can accuse MS, it's using its market position and the VS brand name to "steal" adoption, but that completed before the aquisition too.

Re: Sunsetting Atom

#633
post #218

Earlier quoted context omitted.

The first thing which Visual Studio Code did right was the better performance. The initial reaction to Atom was that it was very promising, but very slow. The second big innovation was the language server protocol.This allowed any language to be supported by VS Code.

Third, for me at least: Remote Extensions. That suite of extensions including SSH WSL, and Container support made things I was already doing frictionless.

Integrated terminal from the get go, built in git interface, and the latest live share.

Re: Sunsetting Atom

#634

Earlier quoted context omitted.

> Emacs, vim Unlike VSCode, Emacs and Vim have a learning curve. And turning them into full blown IDEs makes their usage even more complex. > Sublime Sadly, Sublime is sort of dead. > TextMate TextMate: Text editor for macOS

While I don't know about the plugin ecosystem of Vim/Emacs, I definitely agree with the learning curve part. In Emacs/Vim I can't even escape the program if I don't know a keyboard shortcut. In Vscode even if I forgot Cmd+W/Q I can simply click the close button. Not to mention that all the shortcuts are just globally used shortcuts in all the other software. While I respect praising by the community of Vim/Emacs, I r…

I don't know.

The rare time I use vscode instead of neovim I always end up with a lot of random characters into the code and have to close it without saving for fear of having broken something. You call that user friendly?

Re: Sunsetting Atom

#635

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…

Hi, when can we expect to see some first preview?

Re: Sunsetting Atom

#636

Earlier quoted context omitted.

> Emacs, vim Unlike VSCode, Emacs and Vim have a learning curve. And turning them into full blown IDEs makes their usage even more complex. > Sublime Sadly, Sublime is sort of dead. > TextMate TextMate: Text editor for macOS

While I don't know about the plugin ecosystem of Vim/Emacs, I definitely agree with the learning curve part. In Emacs/Vim I can't even escape the program if I don't know a keyboard shortcut. In Vscode even if I forgot Cmd+W/Q I can simply click the close button. Not to mention that all the shortcuts are just globally used shortcuts in all the other software. While I respect praising by the community of Vim/Emacs, I r…

> In Emacs/Vim I can't even escape the program if I don't know a keyboard shortcut.

Or, you know, you could just click on the File menu and click on Quit.

Re: Sunsetting Atom

#637
post #409

Earlier quoted context omitted.

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?

IMO the killer thing is performance, VSCode starts fast and is smooth to write with. It blew away the older set of Electron-based editors. They work tirelessly on performance every release and it shows imo. Allowing extensions without destroying perf isn't easy either.

Which editor did you came from to think vscode start fast? msword?

Re: Sunsetting Atom

#638
post #409

Earlier quoted context omitted.

IMO the killer thing is performance, VSCode starts fast and is smooth to write with. It blew away the older set of Electron-based editors. They work tirelessly on performance every release and it shows imo. Allowing extensions without destroying perf isn't easy either.

This is why I continued to use sublime text all the way up to capitulating to TypeScript. Code was slower because of all the intellisense. I've had Code freeze on me a few times. Something that I don't have happen in Sublime or Vim. If you have a lot of RAM and work on a current mainstream OS it may seem smooth, but it's still using 400mb of RAM. May as well use Eclipse or WebStorm FWIW. That said I'm using VSCode no…

> "but it's still using 400mb of RAM"

Why does this matter? What is the point of saving RAM instead of using it?

Re: Sunsetting Atom

#639
post #502

Earlier quoted context omitted.

We plan to monetize collaboration. Zed is a collaborative platform disguised as a world-class code editor.

How often do developers want to edit the same file, at the same time, and have those updates occur in real-time? I see this as a compelling feature for something targeting the use cases of, say Google Docs, where multiple people are contributing to an outline document or a business plan at the same time - but for code, I don't quite see the appeal.

I do this all the time. I use a tool that has 2 modes: turn-based and multicursor, the turn-based mode is signnificantly more annoying. Most of the time you just use it to highlight but it's also good to be able to help the other person with typos and comments, while they are focusing on the logic.

Re: Sunsetting Atom

#640

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?

NeoVim can compete on this front. See LunarVim for a heavily extended experience.
Post reply on HN