@mitchellh is it practical to do smaller builds that don’t include the full Unicode tables and either download on demand or simply not support the full range, which I suspect would be fine in the vast majority of cases?

@jon I tried but it destroys IO performance because for every single character we need to go back and forth across Wasm to the browser to call a JS API. Plus, Ghostty has a stupidly optimized SIMD-friendly layout for our Unicode lookups (we use simd128 extensions in wasm).

@psnszsn Theres 2^21 codepoints to compute from codepoint-first. I'm not even sure if JS gives us the data we need to be honest (xterm.js does not do proper terminal-accurate multi-codepoint grapheme processing for example). I have to look.