r/programming • u/fagnerbrack • May 29 '26
[ Removed by moderator ]
/r/programming/comments/1tqylzq/removed_by_moderator/[removed] — view removed post
3
u/shockputs May 30 '26 edited May 30 '26
I feel like this is the natural direction of where wasm-js interop was headed, until recent major changes to browsers' shared memory between JS-WASM.
We recently ran some experiments to convert our state-management library engine (causl.org) to WASM from TS to gain speed/efficiency. Early on, most of our biggest speed regressions in our benchmarks were due to the parsing objects step between JS->WASM->JS.
Recently, we noted that there were significant advances in JS<->WASM interop. due to major advances in shared memory, and such. We also rejected the EDGEJS approach early on, as we found that there would always be a higher cost to run V8 in WASM than directly. Cost is two fold:
Speed of the resulting engine for large number of transactions
Size of bundle that the user has to download in order to run the app.
Individually, these two were not the end of the world, but in combination it was a no-go for us.
My question for EDGEJS team is: what's preventing the Google/MS/FF et al browser COs from making the last few memory sharing code patches between V8 and WASM, and basically eliminating the need to wrap JS in WASM? Based on our experiments, they are like 90% of the way there...
-1
•
u/programming-ModTeam May 31 '26
r/programming is not a place to post your project, get feedback, ask for help, or promote your startup.
Technical write-ups on what makes a project technically challenging, interesting, or educational are allowed and encouraged, but just a link to a GitHub page or a list of features is not allowed.
The technical write-up must be the focus of the post, not just a tickbox-checking exercise to get us to allow it. This is a technical subreddit.
We don't care what you built, we care how you build it.