4 ms·
I have to quibble with blazing fast. What was the resolution on an A3000 or whatever. Pretty low. My recall was the anti-aliased text rendering was technically
by watmough 11y ago
I have to quibble with blazing fast. What was the resolution on an A3000 or whatever. Pretty low. My recall was the anti-aliased text rendering was technically impressive, but practically less-so due to low-resolution. A SUN or Mac was quite a bit nicer. On the Archimedes rendering against a non-solid non-monochrome color was especially nasty.
In that case, caching very expensive rendering to improve performance makes complete sense. Nice Impression summary and screenshot here. http://www.iconbar.com/forums/viewthread.php?threadid=10197 http://www.iconbar.com/forums/viewthread.php?threadid=10197 Bear in mind running on a 4 MHz ARM3 I would think.
Now, with a sufficiently high-resolution display and a performant pixel shader, all the stupid caching and hinting logic can be thrown away, and effort can go instead into optimizing this technique, with no loss of generality, when rendering to arbitrary structures in the page.
- joosters 11y agoSince screen resolutions have scaled far more slowly than memory sizes in the last couple of decades, surely it makes even more sense to cache font rendering nowdays? If we both agree that it was a win for low resolutions (say 640x480), back when a computer might have 2MB of RAM, surely it's far less of a cost now that we have 4k displays (only a few factors bigger) and well over 1000x the amount of memory. Just about everything in computing is a form of caching. It's rarely stupid, so throwing it out is short-sighted.