this post was submitted on 10 Jul 2024
398 points (95.0% liked)
Linux
48315 readers
1103 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's a reason why GUIs don't render fonts in the GPU.
Because it's a pain, there's not much more to it really...
AFAIK it's the copy cost for the memory. GPU makes sense only when the hardware allows this copy to go away. Generally, desktop PCs don't have such specialized hardware.
I don't see why you'd have to copy all that much. Depending on the rendering architecture, once all the glyphs are there you'd only need to send the relevant text data to be rendered. I don't see that being much of a problem even when using SDFs. It's an extremely small amount of data by today's standards and it can be updated on demand, but even if it couldn't it would still be extremely fast to send over every frame. If games do it, so can text editors. Real time text rendering on the GPU is a fairly common practice nowadays, unfortunately not in most GUI applications...
At this point I'm not expert enough to explain more details. You can check font renderers.
Below is what's in my mind but it's just a guess.
In typical PC architectures you have IO between the storage and the RAM, and then there's the copying from the RAM to the VRAM, and editors maybe also want copying from the VRAM to RAM for decoration purposes etc.
I am familiar with the current PC and GPU architectures.
IO is a non issue. Even a massive file can be trivially memory mapped and parsed without much hassle, and in the case of a text editor you'd have to deal with IO only when opening or saving said file, not during rendering.
As for the rendering side, again, the amount of memory you'd have to transfer between RAM and VRAM would be minimal. The issue is latency, not speed, but that can be mitigated though asynchonous transfer operations, so if done properly stutters are unlikely.
Rendering monospaced fonts (with decorators and control characters) at thousands of frames a second nowadays is computationally trivial, take a look at refterm for an example. I suspect non-monospaced fonts would require more effort, but it's doable.
As I said at the beginning, it's not impossible, just a pain. But so is font rendering in general honestly :/
As I indicated, please check (articles and the documentations of) font renderers at this point.