Live data from Hacker News

Sunsetting Atom

github.blog

421–430 of 880 posts

Re: Sunsetting Atom

#421
post #309

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…

Should development ever wind down, you already have the advantage of being able to announce it as "Zed's dead, baby" instead of clunky corporate euphemisms.

In the meantime, zed.dev, baby, zed.dev.

Re: Sunsetting Atom

#422

Earlier quoted context omitted.

We have graphics, but I could see a mode where you `scp` a headless moon lander version of Zed up to a remote server to do remote development. VS Code has a feature like this but I hadn't used it much before switching to Zed full-time.

> VS Code has a feature like this but I hadn't used it much before switching to Zed full-time. Please check it out — being able to edit / run / debug code on a linux server using a mac desktop over ssh, and having the whole experience be as seamless as edit / run / debug locally, is a huge win — it's pretty much _the_ reason that I’m currently using VSCode 90% of the time despite being a huge JetBrains fan (to the po…

It also works on Windows through ssh (including desktop win10), which makes working with Windows easier on the nerves.

Re: Sunsetting Atom

#423

Earlier quoted context omitted.

> Apache Retirement Home for Veteran Projects Honestly, it kind of sucks that at this point you might as well call a project sunset if it has ASF stewardship, and that we seem to practically need the resources of a large company to keep an open source project "truly" afloat. I vastly prefer the honesty in saying "sunset"; it helps bring more light to this situation, and will perhaps drive new approaches to funding fo…

Not everything in ASF is dead. OpenOffice probably is, but NetBeans is still being actively developed . Good thing, too, alongside IntelliJ it was probably the IDE most oriented toward getting people started writing Java code, rather than as a portal into the vast and confusing plugin ecosystem (looking at you, Eclipse).

Back in the day it also had decent PHP support (don't know how true that still is).

Re: Sunsetting Atom

#424
I had high hopes for atom. At first I thought about it as a FLOSS competitor to sublime. Its slowness (mostly because of electron) was entirely tolerable for me even on 10-year old hardware. I was afraid at how fast VSCode ate it. It is a good thing we have VSCodium.

Re: Sunsetting Atom

#425

Earlier quoted context omitted.

I'm cautiously optimistic for https://www.jetbrains.com/fleet/

I just got access to this the other day and I'm excited to try it out!

My initial experience loading a python project was disappointing. I don't know if I didn't configure it right but auto complete and syntax highlighting didn't seem to work properly.

Re: Sunsetting Atom

#426

Earlier quoted context omitted.

yet another buzzword we hear a lot these days: Zed is “lightning fast”… I hear that a lot about Rust projects, like Kitty or Alacritty

"Real real fast"

I like smoke and lightnin'

Bare metal thunder

Re: Sunsetting Atom

#427

Earlier quoted context omitted.

> custom native UI framework Cool project, but this is clearly a contradiction. wxWidgets? That offers a native UI. Wherever possible it uses the UI controls from the underlying OS/system to render the interface. Looking at the project page it describes "a GPU-powered UI framework that met our needs." That's not a native UI. That's a non-native UI compiled to native code, ala something like Flutter.

"Native UI" can be interpreted to mean "UI written in native (i.e compiled to machine) code" or "UI written using the OS's native widgets". You are presuming that the only correct definition is the latter, but it's pretty clear from context that they mean the former.

Yes, you can argue for another plausible interpretation of those two words, but in actual usage "Native UI" has always meant the platform's native UI framework.

Re: Sunsetting Atom

#428
Do not want a "cloud based text editor". Being reliant on an external service is a huge point of failure. It can go down. It can join the huge list of discontinued Google products. It can have security problems. You can be arbitrarily banned by the service operator. Most cloud-based services only live for a few years.

Re: Sunsetting Atom

#429
What was Atom good for, when compared with something like Visual Studio Code?

I recall reading about typing latency and it seemed to come out as one of the slower options: https://pavelfatin.com/typing-with-pleasure/

I guess it would have occupied a similar place as Brackets, another vaguely similar project? https://brackets.io/

Then again, with how popular VSC has become and with how insanely many extensions there are for it, using any other editor feels a bit... counterproductive at times?

Personally, i'm using the following:

  - CLI: nano (vim works too, I just like the simplicity more)
  - Simple text editing: Notepad++ or similar (usually whatever is on the system on *nix)
  - Some scripting, but nothing too serious: Visual Studio Code
  - Development in larger and more complex codebases: JetBrains products (e.g. IntelliJ IDEA, WebStorm and so on)

Re: Sunsetting Atom

#430

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?

We plan to make Zed extensible via WebAssembly, but we're taking a different approach than we did with Atom. Our goal is to make Zed fast, stable, and collaborative first, extensible second. We'll be taking a more conservative approach with our APIs to ensure we can preserve our core values even as users add extensions. Our goal is for Zed to have the lightweight and snappy vibe of Sublime with the power of a more fu…

This is great. Syrus here, from Wasmer.

I think WAPM and Wasmer could help a lot on the extensibility using Wasm plugins. I'd love to chat further, please feel free to reach me at syrus[at]wasmer[dot]io!

Post reply on HN