Live data from Hacker News

Zed on Linux Is Here

zed.dev

241–250 of 703 posts

Re: Zed on Linux Is Here

#241

Does anyone know what is their monetization plan, or if they even have one? Editor with even this much polish takes a lot of time and effort. How is it being funded? Can we expect useful features to progressively get locked behind subscription as it grows in popularity (a la Gitlab)? Edit: Nevermind, found it - https://zed.dev/faq#how-will-you-make-money . Interesting charter. We envision Zed as a free-to-use editor,…

Build a big enough userbase for big tech to want to buy it. It's the only game left outside ads. Worked for WhatsApp, Instagram, Github, Kaggle, etc.

Re: Zed on Linux Is Here

#242
post #193

Earlier quoted context omitted.

Did you have some plugins in vim? It is very odd if it was slower in this scenario.

Not to my knowledge, outside of whatever Debian comes with. Keep in mind this was on a Chromebook - so it would have been running in a VM on a rather memory restricted system. That said, VSCode would have been running in the same parameters. Just found the file. 42MB on a single line. Takes 5 seconds to open in vim, and about 3 seconds for the right arrow to move the cursor one char over. Nothing like gedit, but slow…

I'm pretty sure this is syntax highlighting. It's a known issue to be slow for large files in Vim because it is synchronous. Try starting Vim with syntax highlighting off:

    vim -c 'syn off'

Re: Zed on Linux Is Here

#243

Earlier quoted context omitted.

Not to my knowledge, outside of whatever Debian comes with. Keep in mind this was on a Chromebook - so it would have been running in a VM on a rather memory restricted system. That said, VSCode would have been running in the same parameters. Just found the file. 42MB on a single line. Takes 5 seconds to open in vim, and about 3 seconds for the right arrow to move the cursor one char over. Nothing like gedit, but slow…

I'm pretty sure this is syntax highlighting. It's a known issue to be slow for large files in Vim because it is synchronous. Try starting Vim with syntax highlighting off: vim -c 'syn off'

Yep that helps a ton, thanks. Now it behaves more like nvim, and cursors around much faster -

$ time vim -c 'syn off' tt.json

real 0m3.277s user 0m1.690s sys 0m0.349s

Re: Zed on Linux Is Here

#244
There's something interesting with the light mode / default theme I got after downloading and opening on Apple silicon:

Sidebar contrast is too low, yet, spot on for the wrong contrast ratio target (3.0, for fill, versus 4.5 for text/bg).

I'll file an issue on GitHub eventually, feel free to pass along email in my profile if y'all see this and have someone who is already nerding out on this stuff.

Context on why, and before I get more fuzzy/opinionated, why I'm comfortable speaking to this is some quasi-authoritative tone: I built a new color system that ended up being launched as Material You at Google, at its heart is getting contrast while having expressive colors instead of just flat black/white, so I really appreciate the effort here.

Fuzzy/opinionated territory:

Problem with the low contrast here isn't just that it doesn't literally hit a 4.5 ratio. IMHO this isn't strictly verboten, if I thought that it would mean the engineer part of my brain was too in control. There's an argument to be made its good the sidebar isn't distracted. Problem is disabled states traditionally lower the foreground brightness, so it crosses over into "disabled element" territory when you visually parse it.

Re: Zed on Linux Is Here

#245
post #91

Looks like they're developing their own Apache-licensed GUI framework for this, called GPUI. I think of text handling as one of the trickier parts of building such a framework, so one specifically made to support a text editor would seem to be a pretty good foundation for a general purpose GUI toolkit. I wonder if they (or someone else) will pursue it as an alternative to Qt.

Their toolkit is developed in their monorepo and is not on crates.io nor versionned, so they can do breaking changes any time. Seems risky to use in 3rd party projects.

Re: Zed on Linux Is Here

#247

Earlier quoted context omitted.

I'm pretty sure this is syntax highlighting. It's a known issue to be slow for large files in Vim because it is synchronous. Try starting Vim with syntax highlighting off: vim -c 'syn off'

Yep that helps a ton, thanks. Now it behaves more like nvim, and cursors around much faster - $ time vim -c 'syn off' tt.json real 0m3.277s user 0m1.690s sys 0m0.349s

Interesting. I expected it to be near instant without syntax highlighting but it's still slow.

Re: Zed on Linux Is Here

#248

Earlier quoted context omitted.

This is not a helpful take for you . The same method works fine for me over the last decade. Taking notes helps, having some helper scripts helps. If one’s invested in a technology, one finds a way to remember.

I am glad to hear you have room in your life to tend to idiosyncracies like this.

It’s part of the job. That’s one of the things I’m paid for.

Re: Zed on Linux Is Here

#249

Earlier quoted context omitted.

This is not a helpful take for you . The same method works fine for me over the last decade. Taking notes helps, having some helper scripts helps. If one’s invested in a technology, one finds a way to remember.

You just described how the script is less convenient to meet the preferences of the commenter you replied to. A debian package relieves them of the overhead you describe by having a few people do the work for anyone else that uses the package.

Debian packages are often old. Hence people found a way around.

> You just described how the script is less convenient to meet the preferences of the commenter you replied to.

Well… no. The person I reply to doesn’t say anything about preferences. They want to know how to update the software, the script is the best reference.

Re: Zed on Linux Is Here

#250

Sadly I can't run it in WSL. thread 'main' panicked at crates/gpui/src/platform/linux/wayland/client.rs:143:51: called `Result::unwrap()` on an `Err` value: UnsupportedVersion note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Man, what kinda of QA do they have that they miss something like this? WSL can be considered the second largest Linux "distro". Of course, zed has always felt like an osx first project with linux/windows being second class citizen.

That seems a bit rude. You get the QA you paid for - zero.

And nevertheless, whenever Windows software doesn't work in Wine, you shouldn't think "Wow, how did you fuck that up?". They never promised it'd work in WSL.

Post reply on HN