Live data from Hacker News

We Have to Start Over: From Atom to Zed

zed.dev

231–240 of 243 posts

Re: We Have to Start Over: From Atom to Zed

#231

I really love native apps, but I'm stuck using VS code for now. It just kills me to see how much power goes to blinking the cursor in VS code. I tried Zed for a bit but couldn't make it work. I loved that its so light weight and fast. Looking my all my VS code processes it 3GB vs Zeds 300MB. 1/10 the ram is a meaningful difference. However I really need the Jupyter Notebook support that VS code provides. I'm also too…

How much power goes to blinking the cursor in VS code? And how it compares to other functionally similar editors.

Re: We Have to Start Over: From Atom to Zed

#232

I tried out the editor because of this post: it looks very promising. Unfortunately I can't use it because it doesn't have support for remote hosts/devcontiners. That feature of VScode is critical to my workflow, as I don't actually want to program on a Mac host, but rather use my Mac as a portal to the VMs and containers I actually code on. It massively helps with segmentation of my projects and improves my security…

I switched to Nix on Mac. If dev dependencies are your only problem, there are many non-container solutions for that.

Re: We Have to Start Over: From Atom to Zed

#233

Earlier quoted context omitted.

For some reason they're just called GUIs, but its not just some wrapper, it actually uses RPC iirc. https://github.com/neovim/neovim/wiki/Related-projects#gui There's also the GitHub topic: https://github.com/topics/neovim-guis

Thanks, I'll have a look at those pages in more detail. They did not seem applicable when I first saw them, so ... Mea Culpa?

Its not very obvious if you don't know how it works under the covers that those are just GUIs doing RPC calls, for the most part.

Re: We Have to Start Over: From Atom to Zed

#234

Earlier quoted context omitted.

> make sure you don’t hit the share button Are you concerned using email in general? Because every-time you hit “send” sounds scary as well. Joking aside, it seems fairly obvious that the risk is on you if your “share” your company’s sensitive code.

I don’t most consider these things anymore. How many signed up for copilot without a second thought?

^think

Re: We Have to Start Over: From Atom to Zed

#235
post #230

Earlier quoted context omitted.

A lot of people use hosted git solutions. And even hosted databases!

Someone might even know some unencrypted platform called as GitHub.

I’d argue it’s not quite the same, since with hosted git you are being very explicit in both what you are sharing and who you are sharing with.

Neither of those things are the same here.

Re: We Have to Start Over: From Atom to Zed

#236
post #203
post #115

Earlier quoted context omitted.

Windows support is happening locally on individuals machines. We’ll start upstreaming things up.

Where can we track this work so as to not duplicate it?

I’m trying to get to a point of convergence with 3 different contributors hacking on it right now, and make it a PR. There is also a new “windows-port” channel on Discord. Finally, we are waiting for Zed team to confirm if they are interested to have Windows port in tree at this point.

As a side note, Linux is going pretty strong!

Re: We Have to Start Over: From Atom to Zed

#237

Earlier quoted context omitted.

I would guess most developers do not use vim. Pretending that vim is the universally loved editor that every developer has agreed upon using seems pretty disconnected from the real world. VS Code came up out of nowhere pretty recently, and is used by a lot of people, so that shows that there is (or was, but still post-vim) opportunity for a new editor. Whether Zed is able to gain momentum to cater for the long-tail t…

VSCode came out of nowhere and took the market share previously held by Atom and Sublime Text 2 The folks I know who use Emacs or vim (including me) are by and large still using those tools since before Atom and Sublime got popular. We just have LSP, now, like VSCode does.

And VSCode came about mostly from Microsoft's push. They wanted an "in" for non Microsoft languages, and VSCode gave them that, as well as a Microsoft-provided environment for dotNet on Linux / Mac. This meant that JavaScript / Node developers could still be folded into Microsoft tooling (telemetry) without forcing them into the crushing heaviness of Visual Studio on Windows.

It was a really slick play. Still, it was an overall positive for the profession, and you can still use VSCodium without the telemetry.

Re: We Have to Start Over: From Atom to Zed

#238
post #57

Earlier quoted context omitted.

Vim is just an example. My point was that code at the end of the day is just text, and there's only so many features you need to be able to write/compile/edit efficiently in 99.9% of the cases. Any new power tools for text editing will end up taking more time to learn and remember than be of use.

I'm not so sure. The fact that were editing the code as text and not as mutations and annotations on its syntax tree has always struck me as a sign that we're still in the stone ages when it comes to expressing ourselves precisely to a computer.

If you're using languages that are themselves closer to the syntax tree, then you're part of the way there. Lisps do that. Editor features for most lisps typically include manipulation of syntax-tree-level features like moving forms around. (Emacs comes to mind here.)

Re: We Have to Start Over: From Atom to Zed

#239
post #199

Their custom UI framework might be all fun and games for now, but that will probably change once they realize they need to implement accessibility. Doing this in a custom framework without sacrificing performance won't be easy and is going to require lots of messy, per-platform work. It's not like it's optional for them either. It would be for a simple editor that you can just decide not to use, but they're positioni…

Don’t want to downplay the concern. With modern machine learning is there an opportunity to build a better accessibility tool? Something that works on any set of pixels and sees like a human does? I.e parses text with OCR.

That would be useful if the normal way fails but would always be slower and not as accurate than intentionally implemented accessibility

Re: We Have to Start Over: From Atom to Zed

#240
post #235
post #230

Earlier quoted context omitted.

Someone might even know some unencrypted platform called as GitHub.

I’d argue it’s not quite the same, since with hosted git you are being very explicit in both what you are sharing and who you are sharing with. Neither of those things are the same here.

I misread the above comment it seems, however, my point was that for many it is not instant no, since so many buy space from GitHub et al. Probably most of the small companies.

They have already trust in place. Do they trust Zed too?

Post reply on HN