Live data from Hacker News

Zed on Linux Is Here

zed.dev

271–280 of 703 posts

Re: Zed on Linux Is Here

#271

Earlier quoted context omitted.

I only use editors written in C, as God intended.

This might seem funny until you read Ken Thompson's "trusting trust" paper and realize that bootstrapping Rust is a so overwhelming task that someone implemented a Rust compiler in C++ for this purpose: https://github.com/dtolnay/bootstrap I mean, who knows what kind of malware is transparently being injected in all Rust programs out there.

Nobody wrote a C++ compiler for this purpose; they wrote a Rust compiler (mrustc) in C++.

> I mean, who knows what kind of malware is transparently being injected in all Rust programs out there.

FWIW, using Guix it is very straightforward to build the rust toolchain fully bootstrapped starting from mrustc and gcc.

Re: Zed on Linux Is Here

#272
post #216

Earlier quoted context omitted.

I don't use vanilla xeyes but I use the Window Maker dockapp version ( https://bstern.org/wmeyes/ ) to make it easier to find my cursor on the screen.

Ha. KDE 6 has something like if you jiggle the cursor a certain way, it temporarily grows larger. Better than Windows's function of "hide all my windows"...

I think every OS has this feature. Sometimes it is hidden in an accessibility menu and needs to be turned on.

Re: Zed on Linux Is Here

#273

I tried zed for a few weeks because I'm generally sympathetic to the "use a native app" idea vs Electron. I generally liked it and its UX but: 1. VSCode is pretty damn fast to be honest. Very rarely is my slowdown in my work VSCode loading. Maybe I don't open very large files? Probably 5k lines of typescript at most. 2. Integration with the Typescript language server was just not as good as VSCode. I can't pin down e…

In the morning vscode is ok, come noon, it’s the primary thing eating my battery and it’s getting slower and slower; day end it’s unusable. Sure, restart it, I know, but it’s fairly terrible though.

Re: Zed on Linux Is Here

#274

Earlier quoted context omitted.

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

Paid to screw around with your editor installation? Or paid to edit code.

You know nothing about what I do. Keep editing code. You just grind on an infrastructure brought to you on a silver plate? Like an editor is the only thing we have fuck around with.

That script for the editor is code, too…

Re: Zed on Linux Is Here

#275

Earlier quoted context omitted.

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.

I disagree. They are on front page of HN with "zed on Linux is here". We got to have some standards, don't you think?

WSL is a pretty niche version of "Linux". I would guess that close to 0% of what makes it to the front page of HN had a QA team that explicitly tested it on WSL.

Re: Zed on Linux Is Here

#276
I've kept my neovim config, vscode, and zed configs in parity for a while now. To the point that the keybinds and behaviors are the same (or as simliar as they can be) across all three. In my personal experience zed is eating into the time I use vscode, but not really touching neovim as much. It really has come a long way, and I'm excited I'll be able to use it on my Linux machine without having to jump through hoops.

Re: Zed on Linux Is Here

#277

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

This makes sense. I recently learned that VSCode is clever enough to automatically disable some features (which includes syntax highlighting among I guess other things) when it detects that the file is too big according to some heuristics (like probably, length of the longest line, or maybe just total size of the file).

So IMO I think vim is being "too dumb" here and should be able to adapt like VSCode does. But, meanwhile, if you want to test under equal conditions, you can disable VSCode's optimization by disabling this setting:

Editor: Large File Optimizations

Or directly in settings.json:

    "editor.largeFileOptimizations": false

Re: Zed on Linux Is Here

#278

Earlier quoted context omitted.

Paid to screw around with your editor installation? Or paid to edit code.

You know nothing about what I do. Keep editing code. You just grind on an infrastructure brought to you on a silver plate? Like an editor is the only thing we have fuck around with. That script for the editor is code, too…

I do it all brother. Infrastructure is the fun/easy part.

Re: Zed on Linux Is Here

#279

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…

We'd appreciate the issue and discussion! We've been aware of contrast issues for some time, and I personally have been thinking about switching our color representation from HSL to OKLCH to give us more traction on these problems. But I've been working on Linux and am not a designer, so I haven't had the chance :D

Re: Zed on Linux Is Here

#280

However silly it is, I've always hated the aesthetics of VS Code. I know it's themeable but despite that the overall look and feel just isn't right on MacOS or Linux. That side bar drives me crazy. I find that out-of-the-box Zed is much prettier and feels more native than VS Code. But for a tool that we spend hours using each day, how it looks and makes you feel really matters. I am enjoying experimenting with Zed. I…

The activity bar is the worst. Luckily you can move it and make it smaller.

  "workbench.activityBar.location": "top",

Just in case might as well try these..

  "editor.fontFamily": "'Monaspace Neon', monospace",
  "editor.fontLigatures": "'calt'",
  "workbench.iconTheme": "vs-minimal",
  "workbench.colorTheme": "GitHub Light",

  "window.commandCenter": false,
  "window.customTitleBarVisibility": "auto",
  "window.titleBarStyle": "custom",
Post reply on HN