3 ms·

I feel like this was at least partly written by ChatGPT :) Even if "dynamic high quality text" is hard, I would like to remid you that we're essentially runnin

I feel like this was at least partly written by ChatGPT :) Even if "dynamic high quality text" is hard, I would like to remid you that we're essentially running supercomputers. And most of "dynamic high quality text" on our computers is incredibly static for signinficant amounts of time. Even on CPU we should be able to render any quantity of any quality of any dynamic text at speeds that cannot be perceived by the human eye. (Well, as it turns out, we do exactly that, even on smart phones) And, of course, people have done that, with very little effort. Reason? They actually looked at what a modern computer is capable of, and used that instead of hiding behind high brow "oh, it's beyond PhDs my dear Watson for sho"

vlovich123 4y ago
Nope no ChatGPT. You may want to reread what I said. I was responding to someone talking about games and game performance in the context of text rendering. And the PhD research topic is how to use the GPU to accelerate text rendering. You seem to perhaps be misunderstanding what I’m saying and somehow thinking I’m defending > Microsoft Teams takes 9 seconds to display under a kilobyte of text, including 3 seconds to just display a splash screen) I’m not. Clearly it shouldn’t take that long to render that text. But achieving a screen full of text at 120fps (or is it even just 60fps) on the highest resolution displays is actually a difficult problem for CPU renderers to achieve (even for the greatly simplified case of a single mono space font). If you think otherwise, you may want to sync up with Raph and publish your contributions to this space. It’s possible I’m getting some of the specific details wrong (again - not my area of expertise) but there’s definitely a push to find HW acceleration within the GPU to achieve those frame rates (and not just text rendering - all 2D rendering is difficult to HW accelerate). Notice in [3] how CPU renderers are still lower latency than GPU ones because it’s an area of active research that hasn’t yielded winners yet. Also I’m well aware we have super computers in our pocket. But don’t forget that the screen resolution is really frickin high and DPI scaling on top (so that text is actually legible) adds additional overheads (+ rendering at 60hz instead of 120). There’s also all sorts of tricks being played (eg it’s not going to be rendering the full screen I think because most UIs are retained not immediate). [1] https://raphlinus.github.io/rust/graphics/gpu/2020/06/01/piet-gpu-progress.html https://raphlinus.github.io/rust/graphics/gpu/2020/06/01/pie... [2] https://raphlinus.github.io/rust/graphics/gpu/2020/06/13/fast-2d-rendering.html https://raphlinus.github.io/rust/graphics/gpu/2020/06/13/fas... [3] https://medium.com/@raphlinus/inside-the-fastest-font-renderer-in-the-world-75ae5270c445 https://medium.com/@raphlinus/inside-the-fastest-font-render...

vlovich123 4y ago

Nope no ChatGPT. You may want to reread what I said. I was responding to someone talking about games and game performance in the context of text rendering. And the PhD research topic is how to use the GPU to accelerate text rendering. You seem to perhaps be misunderstanding what I’m saying and somehow thinking I’m defending > Microsoft Teams takes 9 seconds to display under a kilobyte of text, including 3 seconds to just display a splash screen) I’m not. Clearly it shouldn’t take that long to render that text. But achieving a screen full of text at 120fps (or is it even just 60fps) on the highest resolution displays is actually a difficult problem for CPU renderers to achieve (even for the greatly simplified case of a single mono space font). If you think otherwise, you may want to sync up with Raph and publish your contributions to this space. It’s possible I’m getting some of the specific details wrong (again - not my area of expertise) but there’s definitely a push to find HW acceleration within the GPU to achieve those frame rates (and not just text rendering - all 2D rendering is difficult to HW accelerate). Notice in [3] how CPU renderers are still lower latency than GPU ones because it’s an area of active research that hasn’t yielded winners yet. Also I’m well aware we have super computers in our pocket. But don’t forget that the screen resolution is really frickin high and DPI scaling on top (so that text is actually legible) adds additional overheads (+ rendering at 60hz instead of 120). There’s also all sorts of tricks being played (eg it’s not going to be rendering the full screen I think because most UIs are retained not immediate). [1] https://raphlinus.github.io/rust/graphics/gpu/2020/06/01/piet-gpu-progress.html https://raphlinus.github.io/rust/graphics/gpu/2020/06/01/pie... [2] https://raphlinus.github.io/rust/graphics/gpu/2020/06/13/fast-2d-rendering.html https://raphlinus.github.io/rust/graphics/gpu/2020/06/13/fas... [3] https://medium.com/@raphlinus/inside-the-fastest-font-renderer-in-the-world-75ae5270c445 https://medium.com/@raphlinus/inside-the-fastest-font-render...