I built a modern web UI around the v86 x86 emulator so you can boot classic OSes instantly—client-side, no installs. Includes Windows 1.01→XP, ReactOS, Haiku, Android x86, DSL, HBCD, plus custom .img/.iso upload. Would love feedback on performance + UX.
Try it: https://oses.iOblako.com
→ “Launch OS Collection”
How it works / keys: https://oses.iOblako.com/new.html
| Docs: https://oses.iOblako.com/README.md
QEMU in general translates so called "extended basic blocks", then later "chains" them by overwriting the jump instruction [simplification].
This doesn't work well with WebAssembly, because each EBB needs its own module and chaining would be hard to implement since we can't patch existing modules. This is why currently qemu-wasm is so slow.
v86 has a different model of "jitting" the code, but it only supports x86 and each new architecture would require significant rewrites.
I built a modern web UI around the v86 x86 emulator so you can boot classic OSes instantly—client-side, no installs. Includes Windows 1.01→XP, ReactOS, Haiku, Android x86, DSL, HBCD, plus custom .img/.iso upload. Would love feedback on performance + UX. Try it: https://oses.iOblako.com → “Launch OS Collection” How it works / keys: https://oses.iOblako.com/new.html | Docs: https://oses.iOblako.com/README.md
(Built on v86. Credit to the project.)
Is there BeOS somewhere?
Haiku is a reimplementation of BeOS, they are very, very similar, practically the same in many ways.
This is cool, but it is giving me AI generated vibes.
What exactly does yours do that http://copy.sh/v86 doesn't?
See also: https://infinitemac.org/
Android emulator in the browser? That might actually be useful...
Can a host NIC be bridged into the emulated OS?
Unfortunately v86 doesn't support x86_64 and that's why TempleOS is notably missing from the list..
Currently the closest thing is qemu-wasm, but my experiments (chrome only) show that it's still too slow: https://zb3.me/qemu-wasm-test/jspi-noffi/
QEMU in general translates so called "extended basic blocks", then later "chains" them by overwriting the jump instruction [simplification]. This doesn't work well with WebAssembly, because each EBB needs its own module and chaining would be hard to implement since we can't patch existing modules. This is why currently qemu-wasm is so slow.
v86 has a different model of "jitting" the code, but it only supports x86 and each new architecture would require significant rewrites.