Zed on Linux is out!
Zed on Linux is out!
Zed is a modern open-source code editor, built from the ground up in Rust with a GPU-accelerated renderer.
You're viewing a single thread.
I still don't understand why I should need GPU acceleration for my fucking TEXT EDITOR
38 10 ReplyProbably because it's more efficient. GPUs are designed to render things, which editors do. In a text editor, you're effectively rendering fonts over a fixed background, which I assume is pretty efficient using the GPU.
We're not talking about crazy 3D effects here.
Yay to battery savings!
52 2 ReplyShouldn't the DE/Window Manager be handling that? Seems like doing it on a window by window basis would be inefficient (and look inconsistent).
5 2 ReplyThat’s a totally unrelated part of the stack. These days you just have a compositor that combines the output of applications.
The model of out of process rendering in Xorg was done pre-2000s but GPUs became the norm and don’t work well this way.
21 0 ReplyThe model of out of process rendering in Xorg was done pre-2000s but GPUs became the norm and don’t work well this way.
Thats where we get into explicit and implicit sync right?
1 0 ReplyAlso very unrelated, that’s about graphics apis like opengl.
2 0 Reply
The job of the window manager is to manage windows and very little else. Font rendering is done by the widget toolkit, usually via freetype/harfbuzz.
9 0 Reply
Same reason you need it for your terminal (see kitty terminal). It's surprisingly slow to cpu render text, gpu rendering is more power efficient and far more responsive
39 2 ReplyIt was surprising how gpu accelerated rendering helped read logs better. Niche case, but better was better.
18 0 ReplyBetter in what sense?
3 0 ReplyMore readable on my part. The speed at which logs could write to the screen and still be readable was faster for me compared to before.
7 0 ReplyInteresting! I'd like to experience this at some point.
2 0 Reply
Surprisingly slow compared to GPU rendering. But... is it really "surprisingly slow"? If it was some 10mhz machine, then sure... I'd agree with you.
6 1 ReplyLook at the benchmarks on kitty https://sw.kovidgoyal.net/kitty/performance/
5 1 ReplyMaybe I'm missing something, but shouldn't the benchmark be a good approximation to the real workload? I don't see how the measurements reflect the performance difference in real life usages.
Why would I need 100MiB/s processing as opposed to 20MiB/s processing, when I can only read maybe several lines per second?
4 0 ReplyFaster processing means more efficient processing which means less power draw.
https://github.com/kovidgoyal/kitty/issues/2701#issuecomment-911089374
How about keypress latency? Over 3x faster than gnome terminal and 4x faster than alacritty
7 1 Reply
Same reason you need it for your terminal
So I don't.
2 2 Reply
Sppeeed
17 0 ReplyThink about battery life too 🎉
8 0 Reply
I mean, it should be clear. Smooth and fast and snappy. If you don't want that, use neovim like me :)
16 0 ReplyBut... Neovim is smooth, fast and snappy 😭
4 0 ReplyHold down
j
and lmk how smooth it is 😅3 0 Reply😭😭😭
2 0 Reply
Terminals applications are, by definition, not smooth. You can't have smooth scrolling, or anything else really, with a text grid.
3 0 ReplyIdk I'm so used to working in terminal I don't really notice that. For my eyes, it's smooth enough
1 0 Reply
Smooth scrolling? Maybe I'm wrong
5 0 Reply