this post was submitted on 27 Feb 2024
201 points (95.9% liked)

Programming

17025 readers
142 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] eveninghere@beehaw.org 3 points 6 months ago* (last edited 6 months ago)

Edit: I'm writing this out of my ass, so don't quote me.

They wrote that they GPU(I?)-accelerate the font rendering. Well, indeed, fonts are usually rendered with CPUs because it's slow to use the traditional VRAM (which sits in the GPU) for this task, given that the text itself is stuck in the RAM (sitting right next to the CPU). With integrated chips like the Apple Silicon, it probably makes sense to move the font rendering into the GPU because the memory is unified. GTK is absolutely not designed to do this, AFAIK.

But that also means that, to get this particular benefit of their dedicated GUI framework, you probably have to buy an Apple Silicon Mac. There are PCs with similar architecture, iirc, but that also means that there's no way you can upgrade your GPU or RAM individually in the future... My fear is that, on a standard PC, it might be just as responsive as other editors.