Anyone else get ~60-70% CPU usage when moving the mouse around? And no GPU usage.
https://zed.dev/docs/linux#troubleshooting
Let us know if that doesn't fix it!
131–140 of 703 posts
Anyone else get ~60-70% CPU usage when moving the mouse around? And no GPU usage.
https://zed.dev/docs/linux#troubleshooting
Let us know if that doesn't fix it!
Now they just need a flatpak…
https://github.com/zed-industries/zed/blob/main/docs/src/dev...
Earlier quoted context omitted.
> you can't distribute with a shell script for installation Why not? It worked for me.
There are two schools of thought. One strives for correctness, even if that requires extra effort. Another is "anything goes as long as it somehow kind of works more than it doesn't." (Actually it's most probably a spectrum rather than a binary division, but I'm no philosopher or sociologist, so for example's sake I'll operate with this simplified model here.) The world en masse is generally preferring the latter (pi…
And here is even more correct one: https://zed.dev/docs/development/linux
brew install --cask zed
The docs don't make it very clear that the cask is available via homebrew.> To install Zed on most Linux distributions, run the shell script below. This is not an acceptable way to install anything on Linux. If you want to target Linux users you can't distribute with a shell script for installation. I get that the idea is to reduce friction to installation and trying it out, but most Linux users - the ones you want filing bug reports anyway - are ones who will do due diligence and inspect…
I disagree. I’m on Linux for my main installation and I know I can inspect the bash script if I want to. It’s impossible to please everyone. Pipe to sh is simple, transparent, and easy to do. If reading through 200 lines of installation script is too much then reading through thousands of lines of Zed’s code base will certainly be too much. They also list other ways of installing https://zed.dev/docs/linux
Not so transparent[1]. Packages from a package repo are signed, usually with keys not stored on the same server so if someone nefarious breached a server they can easily replace a bash script, they can't re-sign and replace a package.
Sure it's safe if you download the script then review it then install it, but hey, you reviewed it last time, it's probably unchanged, what's the harm of piping it directly to bash next time you need to get set
https://web.archive.org/web/20240228190305/https://www.idont...
I gave it a fair try Cons: - spawning nodejs whenever you edit JSON files seems overkill, i'd prefer they use something native and more lightweight, or a way to completely disable it - text still looks a bit blurry on low DPI screens - doesn't support LSP properly, completion items are missing some data - Rust for plugins.. this is painful, compare it to Sublime Text's python API, it's night and day.. Pros: - Fast an…
Yes, this is unfortunate as they've unsuitably chosen the barely usable & unstable "component model" for their Wasm plugin layer. It's really only half-decent in Rust (to write the code & compile to CM non-standard version of wasm binary. it's also only truthfully usable to call components _from_ rust too.)
I think they are banking on the eventual support for cross-language async - which likely could never come, or could take longer than the company stays solvent!
> To install Zed on most Linux distributions, run the shell script below. This is not an acceptable way to install anything on Linux. If you want to target Linux users you can't distribute with a shell script for installation. I get that the idea is to reduce friction to installation and trying it out, but most Linux users - the ones you want filing bug reports anyway - are ones who will do due diligence and inspect…
It's on NixOS and Arch I'm sure you just wait a little to get it on your Distro... I don't think they have bad intentions.
Even just as a two liner leaves people a copy of what they ran if something goes awry.
Man, I'm conflicted. I mean, Zed works pretty damn well. So far my biggest annoyance with Zed though is that it's constantly trying to download language servers and other tools and run them. And sure, that's handy, but 1. I don't really want it, I'd much rather only use distribution-provided tools. 2. It doesn't work at all on NixOS, so it's just wasting its time and our bandwidth constantly downloading and trying to…
After we finished prepping this linux launch, we've started work on making this situation better. Follow along here: https://github.com/zed-industries/zed/pull/14034
Earlier quoted context omitted.
> Yep, it's the same as running random code with root permissions. It doesn't require root. You can read it before you run.
"reading before you run" eliminates all convenience of the one liner. Their linux docs are way better because it shows you exactly how to do it on a per-distribution basis. when it comes time to update the software I would prefer to know how exactly it is installed so that I can update it correctly.
Then read the script you complain about.