I view stuff like this kind of like code that fits into a bootloader or whatever. It’s really more of the technical challenge than to actually solve a problem. The result is much better if you just run a script on your hand-coded file to add syntax highlighting as DOM elements. Still, love seeing stuff like this.
So script inside web page is bad, but script inside font is good? That's interesting definition of bloat. I'd prefer ordinary webpage using locally installed fonts with explicit JavaScript snippet to highlight keywords.
I view stuff like this kind of like code that fits into a bootloader or whatever. It’s really more of the technical challenge than to actually solve a problem. The result is much better if you just run a script on your hand-coded file to add syntax highlighting as DOM elements. Still, love seeing stuff like this.
So script inside web page is bad, but script inside font is good? That's interesting definition of bloat. I'd prefer ordinary webpage using locally installed fonts with explicit JavaScript snippet to highlight keywords.
Unless I missed it, the OP doesn't quote reducing bloat as a motivation- more just working without javascript.
I took it to be along the lines of an "easier to work with" type motivation, rather than reducing package sizes.
Is it really a script though? IIUC it's more like contextual declaration (e.g. of previous char is X, then use style Y), no?
Remember llama.otf?
> it breaks when your code goes to a newline. there's no way to keep context line to line...
This is a blocker for my applications.
Perhaps you could add this technology to Z80 sans, to get syntax highlighted Z80 disassembly.
https://github.com/nevesnunes/z80-sans