Fluid Simulation and Web Assembly

Fluid Simulation and Web Assembly(ehayes.page)

39 points by nicholasjbs 1 year ago | 7 comments

When on this page almost all my keyboard shortcuts stopped working and it was difficult to close the page. I consider this a form of malware.

pekim 1 year ago | |

The page appears to install global keydown/up handlers that swallow all key events. And it also disables the browser's context menu.

nighthawk454 1 year ago | |

It’s running flawlessly on my iPad mini. Perhaps the site isn’t the issue.

zamadatix 1 year ago | | |

I don't think they mean the performance or anything like that, rather the site literally requests to eat all keyboard events (among other things). To even open dev tools on a completely different system I had to do it via the browser menu as right click, Ctrl+Shift+I, and f12 were set to be globally consumed for input on the site instead of just certain needed events in the app area.

ellellem 1 year ago |

Fluid simulation is more suited to GPU (because particles/molecules...) than CPU. What am I missing? SIMD maybe? Not sure...

s-macke 1 year ago | |

WebAssembly programming is simply easier than GPU programming.

My game here [0] 6 years ago uses WebAssembly with a Finite Difference approach for the fluid part. Nowadays, fixed-width SIMD [1] is standardized and supported in the browser. But I don't now any website using it.

I have tried porting it to WebGPU. It is much more complicated and only Chrome supports it right now. To get fluid simulation working via the older standard WebGL is more like a hack.

[0| https://github.com/s-macke/Interplanetary-Postal-Service

[1] https://github.com/WebAssembly/simd/blob/master/proposals/si...

pornel 1 year ago | | |

https://wgpu.rs can emulate newer APIs on WebGL2. It's really nice to work with.