ksp [il/lui]@jlai.lu to Linux@lemmy.mlEnglish · edit-24 months agoZed on Linux is out!zed.devexternal-linkmessage-square227fedilinkarrow-up1420arrow-down122file-textcross-posted to: linux@programming.devzed@programming.devrust@lemmy.mlprogramming@programming.devfoss@beehaw.org
arrow-up1398arrow-down1external-linkZed on Linux is out!zed.devksp [il/lui]@jlai.lu to Linux@lemmy.mlEnglish · edit-24 months agomessage-square227fedilinkfile-textcross-posted to: linux@programming.devzed@programming.devrust@lemmy.mlprogramming@programming.devfoss@beehaw.org
Zed is a modern open-source code editor, built from the ground up in Rust with a GPU-accelerated renderer.
minus-squareFlorianSimon@sh.itjust.workslinkfedilinkarrow-up53arrow-down2·4 months agoProbably 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!
minus-squarebooly@sh.itjust.workslinkfedilinkarrow-up5arrow-down2·4 months agoShouldn’t the DE/Window Manager be handling that? Seems like doing it on a window by window basis would be inefficient (and look inconsistent).
minus-squareAProfessional@lemmy.worldlinkfedilinkEnglisharrow-up21·4 months agoThat’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.
minus-squareParetoOptimalDevlinkfedilinkarrow-up1·4 months ago 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. Thats where we get into explicit and implicit sync right?
minus-squareAProfessional@lemmy.worldlinkfedilinkEnglisharrow-up2·edit-24 months agoAlso very unrelated, that’s about graphics apis like opengl. https://www.khronos.org/opengl/wiki/Synchronization
minus-squareleopold@lemmy.kde.sociallinkfedilinkEnglisharrow-up9·4 months agoThe 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.
Probably 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!
Shouldn’t the DE/Window Manager be handling that? Seems like doing it on a window by window basis would be inefficient (and look inconsistent).
That’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.
Thats where we get into explicit and implicit sync right?
Also very unrelated, that’s about graphics apis like opengl.
https://www.khronos.org/opengl/wiki/Synchronization
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.