3 ms·
> Since it's more than quick enough to do this on the CPU This is true until it isn't. A modern-ish CPU at 1080p 60hz it'll be fine. At 4k 120hz even the faste
by ben-schaaf 1y ago
> Since it's more than quick enough to do this on the CPU
This is true until it isn't. A modern-ish CPU at 1080p 60hz it'll be fine. At 4k 120hz even the fastest CPU on the market won't keep up. And then there's 8k.
> they're likely doing it for things like animations and very high quality font renderin
Since they're using native render functions this probably isn't the case.
- leecommamichael 1y agoI’m almost nerd-sniped enough to try and see exactly where it breaks down. What’s a native render function? Do you mean just using a graphics API as opposed to an off-the-shelf UI library?
- ben-schaaf 1y ago> What’s a native render function? As in using DirectWrite or GDI on Windows; or Core Text on macOS. As opposed to shipping your own glyph rasterizer.
- hoistbypetard 1y agoDoesn't the blog post specifically say they are shipping their own glyph rasterizer?
- ben-schaaf 1y agoNo? > To work around this limitation, we decided to stop using Direct2D and switch to rasterizing glyphs using DirectWrite instead.