Show HN: Firefox in WebAssembly
This is the entire Firefox browser rendering to a <canvas> element. Gecko, all UI components, and the Spidermonkey JS engine are all compiled and running in WebAssembly. Here are a few things you might find interesting: - This is fully end to end encrypted! We use the WISP protocol for TCP-over-websockets. - There is a novel WASM->JS JIT for experimental site speedup - This port cost over 25k in opus/fable tokens for debugging and JIT research This was just a fun experiment to push the boundaries of WebAssembly. For a more usable "browser in browser" experience, we also built https://github.com/HeyPuter/browser.js that eats a bit less RAM.
Discussion Highlights (20 comments)
throwaway2027
Obligatory https://www.destroyallsoftware.com/talks/the-birth-and-death...
mdlxxv
"Yo dawg. I herd you like web browsers, so I put a browser in your browser, so you can browse the Web while you browse the Web".
eqrion
> There is a novel WASM->JS JIT for experimental site speedup I would love to see the details for this. SpiderMonkey had an attempted wasm32 JIT backend, but it was never finished. edit: Apparently it also has some sort of WebAssembly interpreter backend too, which SpiderMonkey doesn't have.
som
... doesn't support Firefox mobile apparently :D
coolelectronics
Oh and for anyone asking, you can run firefox-wasm inside firefox-wasm inside firefox! I only got this to load once though since it gets pretty unstable at that level.
degamad
I'm so glad this exists, I've been considering doing something like this for a few months. I recently got a TV based on VIDAA os, a locked-down linux-based OS where everything is rendered from Web pages. It has a built-in browser that doesn't support ad-blocking (I suspect VIDAA is profiting from showing ads on the TV), and you can't install new apps unless they're Web pages. This would hopefully allow one to run Firefox within the existing browser, then install uBlock Origin within Firefox... I know what this weekend's project is going to be...
MajesticHobo2
Browser sandboxing is now fully solved.
azakai
Prior art: WebKit.js, the WebKit rendering engine ported to JS https://github.com/trevorlinton/webkit.js/
sangeeth96
edit: I misunderstood, that's $25k not 25k tokens :/ time to log off. this is so rad! 25k tokens is a lot less than i thought this'd take -- what were the difficult bits in the porting process? also, was firefox preferred because parts of it are already in rust?
ohonbob
Since coolelectronics posted his firefox wasm here ill post my sideproject (we worked on these around the same time), Webkit In WebAssembly (And actually modern and usable! Unlike the older trevorlinton/webkit.js project) https://github.com/theogbob/WebkitWasm Not as polished as the firefox port but is a fully working port of webkit ported with fable, opus and some glm 5.2.
jedisct1
"This browser doesn't support WebAssembly JSPI, which Firefox WASM needs to run."
zerof1l
All the network traffic from that browser is routed through a server. My IP inside that browser was in India and on CloudFlare network. I don’t particularly trust Puter. Why not route traffic through my actual browser?
yjftsjthsd-h
>This port cost over 25k in opus/fable tokens for debugging and JIT research > This was just a fun experiment to push the boundaries of WebAssembly I'm a huge fan of the project, but I have to ask. If spending $25k is a "fun experiment", where exactly is your threshold for serious work?
brewmarche
Can’t get it running on Firefox 152.0.6 (aarch64), no extensions. [chrome-demo] chrome assets ready [gecko] warning: unsupported syscall: __syscall_madvise [gecko] embed-xul: main() on the app pthread (PROXY_TO_PTHREAD) [gecko] embed-xul: GECKO_GL_PASSTHROUGH=1 [gecko] embed-xul: GECKO_COARSE_CLOCK=1 [gecko] embed-xul: GECKO_GPU=1 (GPU/WebRender->canvas rendering) [gecko] xul_init: GRE dir = /gre [gecko] Pthread 0x11051000 sent an error! blob:https://developer.puter.com/edc1bd0a-b844-4a18-a69a-63dd49dc304a:8906: SecurityError: Security error when calling GetDirectory
simonw
This is amazing. I loaded up https://developer.puter.com/labs/firefox-wasm/ in Chrome and I've visited a bunch of sites, it works really well. Then I opened up https://developer.puter.com/labs/firefox-wasm/ in Firefox-in-WebAssembly-in-Chrome ... and sadly it didn't load. I got this in the startup log: [log] [chrome-demo] chrome assets ready [warn] [gecko] warning: unsupported syscall: __syscall_madvise
SpyCoder77
No mobile support
koolala
What makes it require that WASM extension you need the flag for in Firefox? Was there really no way to work around it or polyfill it for it to work? It is performance critical?
elmer2
I would be careful with this demo. When you go to whatismyip.com, it's showing: 104.28.233.73. Someone could use this to cloak their IP address and do some damage.
andai
The description mentions a similar project browser.js which apparently has some real use cases, what are they?
luciana1u
25k tokens to port Firefox to WASM. by 2027 we'll be spending 25k tokens to port WASM back to native because someone will benchmark it and find the WASM version is 3% faster.