2026-07-25 03:40 UTC
When designing a hardware-browser I found that the string-centric CPU designed could easily choose fonts, resolve bidirectional text, & otherwise preprocess text for rendering. But when I designed a coprocessor to (concurrently) mathematically negotiate layout, I found it'd need to layout the text as part of that negotiation. Which in turn necessitated an extension letting it consult (small-ish) lookuptables, in addition to dangling the font's Binary Search Trees off the layout tree.
4/6?
Replies (1)
-
@alcinnz@floss.social 2026-07-25 03:49
Or in that hypothetical... Early-boot could omit could omit the fancy layout, & layout text once at a given width. Then it can be left to the strengths of the string-centric CPU I designed. For an "idiomatic" vectorized 32bit computer with raw memory-mapped I/O... In addition to code & data SD card slots I resorted to including a 3rd cartridge slot for localized text handling code. Presuming this machine could get away with serving only its direct user. 5/6?