yeah why would anyone want to run code on a website

bqmjjx0kac 5 days ago | parent | next [-]

It would be more plausibly practical if GHC could now target wasm, but this announcement is actually about being able to run the compiler itself in the browser.

	▲	tempay 5 days ago \| parent \| next [-]
		It can target wasm, the point of the post is that it’s now mature enough to be able to build itself for wasm and run in a browser.
	▲	Jaxan 5 days ago \| parent \| prev \| next [-]
		This is a show case of the wasm backend
	▲	whateveracct 5 days ago \| parent \| prev [-]
		GHC is built with GHC lol

▲

swannodette 5 days ago | parent | prev [-]

Loading 50mb of WASM is a big tradeoff just to run code on a website.

	▲	tuveson 5 days ago \| parent \| next [-]
		Loading time is pretty rough, but it seems responsive enough after the initial load. Probably as fast or faster than downloading and installing GHC locally.
	▲	extraduder_ire 5 days ago \| parent \| prev \| next [-]
		For comparison: the homepage of cnn.com right now is 33.37MB on my machine. 16.82MB of which is JavaScript.
	▲	wslh 5 days ago \| parent \| prev [-]
		I would assume that in the near future one can preload, cache, update selected WASM packages. I also imagine that sooner than that we can preload open models in the browser to run the natively instead of only invoking third parties (e.g. window.ai in the DOM)