31–40 of 60 posts
I don't get it, why there's no link to a GitHub pages website to test the thing?
You can't test it in a browser, since no browser at present is linked against libharfbuzz with WASM shaper. Instead, one can test it with a modified local program such as gedit in the demo. As convenience, I built a Docker image that packs both the ttf file and the modified gedit together. You can try it out via `make run` as stated in the instructions.
Earlier quoted context omitted.
but... the program ends up entirely compiled and executed as TTF bytecode in the end right, since it's entirely contained in the TTF font ? And TTF bytecode is only the following instructions : https://developer.apple.com/fonts/TrueType-Reference-Manual/... and I don't see anything related to SIMD in there
No that is not what is happening, HarfBuzz have a experimental Wasm shaper, so the font embeds some wasm code that tells Harfbuzz what to output. https://github.com/harfbuzz/harfbuzz/blob/main/docs/wasm-sha...
Earlier quoted context omitted.
You can't test it in a browser, since no browser at present is linked against libharfbuzz with WASM shaper. Instead, one can test it with a modified local program such as gedit in the demo. As convenience, I built a Docker image that packs both the ttf file and the modified gedit together. You can try it out via `make run` as stated in the instructions.
If you just want to run locally. Why not using the native libharfbuzz directly? What's the purpose of WASM here?
It's an experimental feature, so it's not available unless explicitly enabled during compilation.
I bet this is what people felt when JavaScript was first demoed on the web. In the year 2077, when each font will run it's own virtual machine on WASM containing a "minimal" Ubuntu image, some enlightened blogger will suggest server side rendered fonts as a performance improvement.
OP's repository has a Makefile which assumes a docker daemon is available.
The project must be tested in an application linked against libharfbuzz with WASM shaper enabled. Since it's not easy to build a library like this, I make a Docker image which contains both the ttf file and a modified gedit, so that anyone can test the project with a single command.
I don't get it, why there's no link to a GitHub pages website to test the thing?
You can't test it in a browser, since no browser at present is linked against libharfbuzz with WASM shaper. Instead, one can test it with a modified local program such as gedit in the demo. As convenience, I built a Docker image that packs both the ttf file and the modified gedit together. You can try it out via `make run` as stated in the instructions.
I bet this is what people felt when JavaScript was first demoed on the web. In the year 2077, when each font will run it's own virtual machine on WASM containing a "minimal" Ubuntu image, some enlightened blogger will suggest server side rendered fonts as a performance improvement.
JS felt less impressive to me when I first saw it, simply because it couldn't do much. However, I remember the showcase Microsoft put together to show off what CSS could do in IE3 and that was very cool at the time.
Nice demo. Without trying to steal the thread, what I would care is actually the opposite direction. Neither in Swift Playgrounds, nor in any other programming development environment apps for both mobile OSes, have I found a good development experience using pen instead of keyboard. Given how many of us "program" in paper notebooks, it is quite incredible that besides a couple of research projects done by PhD studen…
In the same way that the calculator writes in the answers in your handwriting, it could write in snippets of code in your handwriting.
If it's going to be made though, it has to be e-ink. Go big or go home!