I’m very mixed about WASM. It’s clearly a very cool technology, and enables cool things by allowing native performance without needing multi-platform support.
But at the same time, it provides a vector for foreign, non-free software to run on my computer. Every time someone sends me a Google doc blocking printing/copying (on _my_ computer!), it makes me want to join a monastery.
Can already see a nice web based AI app builder on the way, also can be used to quickly try apps before pushing to the device as interactive app store.
Please watch out some qemu targets for Cortex m0 or m3, increasing ram from linker out of supported ranges will cause random crashes. Would love to contribute if you are looking for people to crash some issues.
Love the idea, would be great to see a modes to switch to circular interface for the Time Round 2. Definitely lots of potential for rapid iteration on new watch faces and apps!
18 comments
[ 5.4 ms ] story [ 37.4 ms ] threadBut at the same time, it provides a vector for foreign, non-free software to run on my computer. Every time someone sends me a Google doc blocking printing/copying (on _my_ computer!), it makes me want to join a monastery.
- using native exception handling
- getting rid of asyncify (but it would require JSPI)
See my experiments with TempleOS here: https://zb3.me/qemu-wasm-test/
found an assertion just by clicking up/down. doesn't seem too stable.
Please watch out some qemu targets for Cortex m0 or m3, increasing ram from linker out of supported ranges will cause random crashes. Would love to contribute if you are looking for people to crash some issues.
Awesome effort btw.