99 times out of a hundred, sure. But sometimes you need better performance or a library that isn't available in JS.

hollowturtle 8 days ago | parent | next [-]

Better performance? For javascript code that calls into native platform apis provided by the browser it's been alteady proven that performance is an order of magnitude better than calling into wasm and doing all the sheningans to move bytes from and to wasm

▲

ramses0 8 days ago | parent | prev | next [-]

Or even "use server.physics.go", which is where my mind went to (and where I've messed around with language interoperability with tinygo before).

This is such a wonderfully blursed and "smooth" implementation!

▲

pjmlp 8 days ago | parent | prev [-]

WebGPU or WebGL is the answer.

	▲	dgb23 8 days ago \| parent [-]
		I second that, having just relatively recently used the native browser APis for image processing. While it felt a bit awkward to use, it served its purpose pretty well. If I needed more, I would probably not use Go anyways, but a sharper tool instead.