vortex VS python-wasm

there have been quite a few threads about "reasonably priced" FPGA platforms and https://github.com/vortexgpgpu/vortex/blob/master/docs/fpga_... will interest you, but regrettably I haven't ever tried to use an FPGA to speak to whether their verilog only targets one of them, or "bring your own," and for sure I'm not the right person to speak to how much such a stunt would cost

It would make for a helluva blog post, though, or set up a shopify selling pre-made ones for people like you :-)

vortexgpgpu/vortex (github.com)

Open source RISC-V GPGPU\ (29 comments)

This wouldn't work, you should just use python-wasm to run the cpython interpreter on the browser.

Thanks for the detailed explanation, makes complete sense.

I suppose that means that for projects such as python-wasm [0] that are porting other language runtimes to WASM they will have to go the Asyncify route with all the overhead that entails?

From the looks of it they don't think asyncifying Python will be possible in the near to medium term [1].

0: https://github.com/ethanhs/python-wasm

1: https://github.com/ethanhs/python-wasm/issues/12

Ethan Smith, a Berkeley-based software developer, recently revealed a project that allows CPython, the default implementation of the Python programming language, to run within web browsers via WebAssembly, or WASM.