5 ms·
I guess if you have a use case with higly cacheable data on edge, it might work great. For example, a form builder like typeform could cache form definitions o
by eknkc 2y ago
I guess if you have a use case with higly cacheable data on edge, it might work great.
For example, a form builder like typeform could cache form definitions on edge and render them close to users. Submissions would require db communication but the entire experience could be better.
Otherwise it is just not worth it.
BTW, I don’t even think PHP running slower in wasm would be that important. These things generally depend on IO performance rather than runtime if you are not doing a lot of calculations on the edge. WASM is also pretty fast these days so..
- 1oooqooq 2y ago> WASM is also pretty fast these days so.. ironically everything is petty fast and everyone waste that speed adding things that allow for a cheaper labour. wasm included. it went from a "have some expertly optimized code in the browser" to "just compile this hide cpp thing and ship as a react component" to then "it allows our servers to run any crap without knowledgeable staff in each language" we added so many Layers to cheapen labour that now all the labour costs goes into managing the Layers.
- eknkc 2y agoOk hear this, I was toying with zig last week and compiled a quickjs wrapper that can run React and compiled that to wasm. So I have a JS runtime running wasm which runs quickjs runtime via zig and that runs React. Just trying to learn zig though but not much different than running PHP in WASM haha. Layers and layers of shit pressed together.
- 1oooqooq 2y agowill definitely use it as the wrapper that launches my electron app