Live data from Hacker News

Zed, a collaborative code editor, is now open source

zed.dev

541–550 of 642 posts

Re: Zed, a collaborative code editor, is now open source

#541

Earlier quoted context omitted.

I have now: https://github.com/zed-industries/zed/issues/6440

For people following along at home, this was fixed with a 250x speed up (!) in https://github.com/zed-industries/zed/pull/6700

And for OPs comment! https://x.com/thorstenball/status/1750489879912349894?s=20

Re: Zed, a collaborative code editor, is now open source

#542
post #180

Earlier quoted context omitted.

I'd suggest that the people who make "full use" of vsc-over-ssh are satisfied with vscode, so it would be unwise to target the full featureset. More generally, targeting another project's complete featureset is often a great way to get mired down in the wrong details. Unless you can afford to do a proper cleanroom -- then, you'll be able to at least match the performance and useful abstractions used in the original.

> I'd suggest that the people who make "full use" of vsc-over-ssh are satisfied with vscode, so it would be unwise to target the full featureset. Remote SSH + Dev Containers and their seamless integration (even stacking one on the other) are the only features that keep me using VS Code. I would love to see the full implementation of these in an editor as fast and light weight as Zed.

How exactly are these features present in your workflow? I honestly struggle to think of when I'd ever use this.

Fwiw, I do a lot of infrastructure-as-code, full stack, and systems programming.

I usually have a split screen (editor | terminal) or two terminals on the side, and exec into a container, or use devenv.sh.

If I _really_ need to modify files in the container as I dev and a "make" doesn't cut it, I usually just run podman with a -v mount. Similarly for remote machines w/ sshfs, though I try not to.

Re: Zed, a collaborative code editor, is now open source

#544
post #449

> GPUI rasterizes the entire window on the GPU, just like a 3D video game. So my laptop will be roasting hot constantly?

No, because a game utilizes the GPU 100% most of the time, while the simple GUI of this editor doesn't require as much calculations (fewer triangles, etc.). So your GPU can downclock and stay cool and quiet.

Re: Zed, a collaborative code editor, is now open source

#545

No way can I use a text editor that requires the hi-perf discrete gfx card. My battery just can't take it. Hope I can get all my work done in about 1.5 hours, because that's how long the 2019 16" mpb will last with the discrete card running.

It doesn't require a discrete graphics card, it can run just fine on the integrated one.

Re: Zed, a collaborative code editor, is now open source

#546
post #446

Earlier quoted context omitted.

Zed developer here, You can come try it out with us right now if you like: https://zed.dev/channel/zed-283 Though you'll have to sign the CLA first :)

This looks really cool, but I have a suspicion my employer would be against external connections. Any distant plans in the future for an enterprise/onprem license?

Yes! In fact, that's one of our planned revenue sources, once we've fleshed things out :D :D

Re: Zed, a collaborative code editor, is now open source

#547

Earlier quoted context omitted.

The core app itself is 100% Rust, but it supports integration via Microsoft's Language Server Protocol[0][1]. In practice, this means you will be running daemons locally for each language, which may be written in any language. Often these daemons are written in NodeJS since the reference implementation[2] is in NodeJS. [0] https://zed.dev/docs/adding-new-languages#lsp [1] https://microsoft.github.io/language-server-p…

It doesn’t follow that a language server written with JavaScript and run via node will bloat the binary by hundreds of MB. Are they bundling a node runtime too? Maybe if they are embedding dozens of language servers and runtimes it could bloat the binary, but I assumed the extensions and language servers would be downloaded on demand. But a rust binary by itself shouldn’t be that large. LSP is just a simple json prot…

When I opened a Rust project I think the status bar said it was downloading Rust support, which supports your hypothesis. (Also it doesn't make much sense to bundle these things when they are all making new releases at different schedules.)

Re: Zed, a collaborative code editor, is now open source

#549
post #547

Earlier quoted context omitted.

It doesn’t follow that a language server written with JavaScript and run via node will bloat the binary by hundreds of MB. Are they bundling a node runtime too? Maybe if they are embedding dozens of language servers and runtimes it could bloat the binary, but I assumed the extensions and language servers would be downloaded on demand. But a rust binary by itself shouldn’t be that large. LSP is just a simple json prot…

When I opened a Rust project I think the status bar said it was downloading Rust support, which supports your hypothesis. (Also it doesn't make much sense to bundle these things when they are all making new releases at different schedules.)

Hey, Zed developer here. Indeed we do not bundle the LSP binaries into the final binary for the reasons you've stated; and I do agree that the binary is kind of big, though at present .dmg compression gets us a long way (as the .dmg itself is ~115Mb). Right now we ship an universal binary, so half of that size is essentially unused:

  size /Applications/Zed.app/Contents/MacOS/zed
  __TEXT __DATA __OBJC others dec hex
  120979456 475136 0 4336828416 4458283008 109bc0000 zed (for 
  architecture x86_64)
  117587968 458752 0 4336680960 4454727680 10985c000 zed (for 
  architecture arm64)
Then, each of these binaries includes about 40MB of assets. I've actually had a PR up (https://github.com/zed-industries/zed/pull/3997) that reduced their size quite significantly, though that did not end up reducing the size of a .dmg itself, so I've scraped that. On top of that, we ship with debug symbols for symbolication of crashes (https://github.com/zed-industries/zed/blob/main/Cargo.toml#L...).

Re: Zed, a collaborative code editor, is now open source

#550

Earlier quoted context omitted.

You know Windows is the most common development platform? If it were me I'd prioritize it

I think linux + osx combined is probably developer majority. I'm assuming most Windows development is .NET or Unity based. Over the past nine years, I've worked primarily with Node, Ruby, and a smidgen of Java and no employer has issued Windows machine. It's in sharp contrast with the start of my career where I was in VB6 and C# where I only worked with Windows environments. Could be confirmation bias, though.

Windows is a great platform for developing any language or platform, not just .Net. Personally I think it blows macOS and its dated tools out of the water in any category

https://survey.stackoverflow.co/2023/#section-most-popular-t...

Stackoverflow found that Linux and macOS is the slight majority for professional use and the minority for personal use with developers (with the caveat that the total professional use of all categories is >100%)

Post reply on HN