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.
Awesome effort btw.
KetoManx64 8 hours ago [-]
I'm blow away at what Devs are able to do within a browser nowadays.
pjmlp 3 hours ago [-]
You could have done the same with plugins in the past.
afavour 28 minutes ago [-]
And now we don't need to use them and expose ourselves to security vulnerabilities. Win win.
bossyTeacher 6 hours ago [-]
More that browsers have gotten sprouted downwards and obtained all sorts of low level access than older browsers didn't use to have. I believe this is partially why tools that were meant to just render markup have gotten so complex to build that a small team of devs is not enough to build a modern browser anymore. And by that I mean from scratch, not just piggybacking on Chromium or Gecko.
idle_zealot 5 hours ago [-]
> I believe this is partially why tools that were meant to just render markup have gotten so complex to build that a small team of devs is not enough to build a modern browser anymore.
Isn't it basically the opposite? The hard parts of the browser are layout, styling, and multimedia stuff that goes into rendering markup compliantly. Then there's the infinite sink of optimization work for a JS engine, the high-level scripting language for that markup. The low level access that something like this emulator use is comparatively easy; a WASM runtime and Canvas blitting pixels from some shared buffer.
Or am I mistaken that a WASM engine is much easier to build than a performant JS engine?
nomel 6 minutes ago [-]
> Or am I mistaken that a WASM engine is much easier to build than a performant JS engine?
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.
Isn't it basically the opposite? The hard parts of the browser are layout, styling, and multimedia stuff that goes into rendering markup compliantly. Then there's the infinite sink of optimization work for a JS engine, the high-level scripting language for that markup. The low level access that something like this emulator use is comparatively easy; a WASM runtime and Canvas blitting pixels from some shared buffer.
Or am I mistaken that a WASM engine is much easier to build than a performant JS engine?
Absolutely. It's very limited, and designed for purpose, rather than somewhat by mistake (like JS): https://github.com/sunfishcode/wasm-reference-manual/blob/ma...
found an assertion just by clicking up/down. doesn't seem too stable.
- 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/