3 ms·
> Offloads rendering to the GPU I don't understand this - isn't all rendering on a typical macOS or Linux desktop done via the GPU?
by chrisseaton 6y ago
> Offloads rendering to the GPU
I don't understand this - isn't all rendering on a typical macOS or Linux desktop done via the GPU?
- markstos 6y agoI believe the software has to take advantage of the GPU. The `foot` terminal renders on the CPU instead of the GPU, but beats GPU-accelerated `alacritty` anyway due to other effiency hacks described on their Performance page: https://codeberg.org/dnkl/foot/wiki/Performance https://codeberg.org/dnkl/foot/wiki/Performance
- chrisseaton 6y agoHmm I think it's more the case that an application has to go out of its way to not render on the GPU. High level frameworks' basic rendering operations are, of course, always GPU accelerated. They'd be crazy not to be! It looks like Foot is rendering using CPU by talking directly to the compositor.
- AstroNoise58 6y agoThere are various ways to take advantage of the GPU -- the so-called GPU-accelerated terminals contain bespoke OpenGL programs ("shaders") to do rendering on the GPU. Here's an interesting way of doing it: https://tomscii.sig7.se/2020/11/How-Zutty-works https://tomscii.sig7.se/2020/11/How-Zutty-works
- dharmab 6y agoSpecifically, kitty uses VRAM as a font rendering cache: https://sw.kovidgoyal.net/kitty/performance.html https://sw.kovidgoyal.net/kitty/performance.html
- chrisseaton 6y agoRight... but doesn't every serious desktop GUI framework already do that? They aren't drawing every glyph every time from the original curves, and where else would they store video data than... the video RAM.