box2d-wasm VS comlink

https://github.com/Birch-san/box2d-wasm.) Godot uses box2d, too, so that would be convenient, if I switch to godot, but only if it is worth the performance improvement, which it currently does not seem to be. Maybe next year.

Following the article, you build a simple 2D physic simulation (only for balls). Did by chance anyone expand on that to include boxes, or know of a different approach to build a physic engine in WebGPU?

I experiemented a bit with it and imolemented raycasting, but it is really not trivial getting the data in and out. (Limiting it to boxes and circles would satisfy my use case and seems doable, but getting polygons would be very hard, as then you have a dynamic size of their edges to account for and that gives me headache)

3D physic engine on the GPU would be the obvious dream goal to get maximum performance, but that is really not an easy thing to do.

Right now I am using a Box2D for wasm and it has good performance, but it could be better.

https://github.com/Birch-san/box2d-wasm

The main problem with all this is the overhead of getting data into the gpu and back. Once it is on the gpu it is amazingly fast. But the back and forth can really make your framerates drop - so to make it worth it, most of the simulation data has to remain on the gpu and you only put small chanks of data that have changed in and out. And ideally render it all on the gpu in the next step.

(The performance bottleneck of this simulation is exactly that, it gets simulated on the gpu, then retrieved and drawn with the normal canvasAPI which is slow)

box2dwasm - an old, still maintained C++ library compiled to WASM. The documentation is lacking and developer experience seems poor.

network inspector says 2.1MB. but that's dominated by a 1.3MB image.

the main assets of the library are:

- Box2D.simd.js (422kB)

- Box2D.simd.wasm (266 kB)

a minimal demo that uses the library can be created in just a few kB:

https://github.com/Birch-san/box2d-wasm/tree/master/demo/mod...

A couple weeks ago I ported liquidfun to TypeScript + WebAssembly: https://github.com/Birch-san/box2d-wasm/releases/tag/v4.0.0-liquidfun.0

Feels like taking a general Comlink-like system & making it more component oriented. Good ideas. https://github.com/GoogleChromeLabs/comlink

React UI Framework: https://ant.design/ Reactive: https://www.learnrxjs.io/ Workers: https://github.com/GoogleChromeLabs/comlink Graphics: https://www.pixijs.com/

Reminds me of Comlink

Now that we have a way to create PDF files, we can create a web worker to run the renderPDF function in a separate thread. Here’s an example of a web worker that uses comlink to expose the renderPDF function as an asynchronous function:

To streamline the process of configuring the Service Worker and simplify communication between the app and the Service Worker, we will be using the comlink library.

While there's no realistic way to provide a security boundary between JavaScript modules, Workers are a possibility [1].

The code with the more restricted set of permissions must run in the Worker. That code then communicates with the rest of your app through postMessage / SharedArrayBuffer, perhaps using ComLink [2].

[1] https://deno.land/[email protected]/runtime/workers#specifying-...

[2] https://github.com/GoogleChromeLabs/comlink

The worker API is very simple, you would post a message to the worker. The worker would have the code to process and reply back with the results to the listeners. To make it even easier Google has created the comlink library.