梁海 Liang Hai
@lianghai.dev
https://lianghai.dev (That’s the Slow Horses staircase in the banner pic, in case you were wondering.) #Unicode #OpenType #Python #TypeScript #Svelte #Astro #Swift
- On the other hand, Google Fonts has been porting tools to Rust. You can read about their roadmap here: github.com/googlefonts/..., where klippa is mentioned as a replacement of hb-subset.
- You should also keep an eye on the progress of the Incremental Font Transfer effort: www.w3.org/TR/IFT/.
- You should also keep an eye on the progress of the Incremental Font Transfer effort: www.w3.org/TR/IFT/.
October 13, 2025 at 9:02 PM
- On the other hand, Google Fonts has been porting tools to Rust. You can read about their roadmap here: github.com/googlefonts/..., where klippa is mentioned as a replacement of hb-subset.
- You should also keep an eye on the progress of the Incremental Font Transfer effort: www.w3.org/TR/IFT/.
- You should also keep an eye on the progress of the Incremental Font Transfer effort: www.w3.org/TR/IFT/.
- Likely irrelevant to you, but fyi, the corresponding solution in Python (the font industry’s common language) is maintained by pretty much the same group of developers in fontTools: glyph set subsetting (github.com/fonttools/fo...) + design space subsetting (github.com/fonttools/fo...).
October 13, 2025 at 9:02 PM
- Likely irrelevant to you, but fyi, the corresponding solution in Python (the font industry’s common language) is maintained by pretty much the same group of developers in fontTools: glyph set subsetting (github.com/fonttools/fo...) + design space subsetting (github.com/fonttools/fo...).
- Fonts are complicated. Don’t trust naive solutions that are not backed by HB developers.
- HB has a WASM-based JS lib, harfbuzzjs (github.com/harfbuzz/har...), which is currently maintained in a quite confusing way and can use some help from professional TS developers (github.com/harfbuzz/har...).
- HB has a WASM-based JS lib, harfbuzzjs (github.com/harfbuzz/har...), which is currently maintained in a quite confusing way and can use some help from professional TS developers (github.com/harfbuzz/har...).
October 13, 2025 at 9:02 PM
- Fonts are complicated. Don’t trust naive solutions that are not backed by HB developers.
- HB has a WASM-based JS lib, harfbuzzjs (github.com/harfbuzz/har...), which is currently maintained in a quite confusing way and can use some help from professional TS developers (github.com/harfbuzz/har...).
- HB has a WASM-based JS lib, harfbuzzjs (github.com/harfbuzz/har...), which is currently maintained in a quite confusing way and can use some help from professional TS developers (github.com/harfbuzz/har...).
(Oops I meant “expression-only”.)
October 12, 2025 at 10:38 AM
(Oops I meant “expression-only”.)
Naming is easy. A successor to JSX is naturally named with the next letter, so JSY – Y for “WHY are you still tolerating a statement-only syntax?”.
October 12, 2025 at 12:00 AM
Naming is easy. A successor to JSX is naturally named with the next letter, so JSY – Y for “WHY are you still tolerating a statement-only syntax?”.
Ah turned out you’re a co-chair of TC39! No wonder I vaguely heard you mentioned “standardization” several times to people… 🫠
October 10, 2025 at 11:47 PM
Ah turned out you’re a co-chair of TC39! No wonder I vaguely heard you mentioned “standardization” several times to people… 🫠
