Live data from Hacker News

Zed on Linux Is Here

zed.dev

701–703 of 703 posts

Re: Zed on Linux Is Here

#701

Earlier quoted context omitted.

Why? I’m going to run their software anyways. And this is a really easy way to run an installer. This is basically the Linux equivalent of download and double click which is a user flow that is underrated for simplicity and usability.

Completely agree. Furthermore, you could always just not pipe it to sh, read it first if you care so much. Releasing and maintaining packages across a range of distros is extremely hard and time consuming, and they just released the linux version.

> Releasing and maintaining packages across a range of distros is extremely hard and time consuming

That's why Flatpak exists

Re: Zed on Linux Is Here

#702
post #587

Earlier quoted context omitted.

Enforcing auto-formatting is a common practice in my experience. Currently working on a project where the repo will refuse commits that are not following the repo-specific formatting settings. I think it is a sane default in 2024.

No, it isn't. And anyway, I downloaded a generic text editor which has no idea of what autoformatting settings are applicable to my repos (maybe it differs per repo?), yet is trying to autoformat anyway? For example, it decided to replace ' characters in a YAML file with ". WTF? The _default_ setting should be to save as-is.

> maybe it differs per repo

Then you'll already have a formatter config file in the root of your repo, and the formatter that Zed runs will use those settings.

Re: Zed on Linux Is Here

#703

Earlier quoted context omitted.

> Holy sh*t, they actually have bindings for each OS and built a Rust abstraction on top of that. That's pretty wild I grew up developing Windows apps using the native Win32 API:s, and there was nothing particularly daunting about it. Using what the OS provides shouldn't be considered such an outlandish idea, and being scared of it is causing stagnation and waste (looking at you, Electron). The code here is only a co…

I'm not sure how much of it is people being (irrationally) scared vs. looking into native APIs and making the call that it just isn't worth it, given how much messing around you have to do to get basic functionality working vs. the web where you can throw a UI together very quickly to validate an idea. I've looked into native Linux development a few times, for example, and haven't even been sure what's the best toolk…

Sure, you can get stuff out faster by using a web view, but it will suck. It's the usual conflict between speed of development vs control. In the 90s we had Visual Basic for that, but if you were serious about quality you would use something lower level.

Linux is kind of a special case because its ancient ancestry and open philosophy means it doesn't offer standard UI components at all (and with Wayland, there's not even a standard API for creating windows). You either draw the pixels yourself on the screen or you use some library for it. But if you're targeting primarily KDE you would use QT, and if you target primarily Gnome you use GTK.

With MacOS and Windows there is a rich set of standard UI controls implemented by the OS, that ensure integration with the OS and a consistent look & feel. When you use a webview you lose all that.

Post reply on HN