3 ms·
Step 1) Find a language that can do that Step 2) Compile it to WebAssembly Step 3) Validate those input fields Step 4) Profit
by tiborsaas 7y ago
Step 1) Find a language that can do that
Step 2) Compile it to WebAssembly
Step 3) Validate those input fields
Step 4) Profit
- wruza 7y agoI better wait a decade, it ain’t much competition since we’re all in the same boat. It’s nice that many are happy with what we have now, but I don’t understand why you dismiss this suggestion so easily (and superficially, as it seems). Wasm doesn’t allow 1+2, since browsers dictate how io/device/extension-communicating code should be done and their native routines are not ready for techniques of the level higher than just a bare callback. Wasm is not a solution, since the platform and primitives are the same. It is basically the same javascript-in-a-browser model with syntax and scoping rules to be implemented by someone else. One can emulate any language by turning js/wasm into a virtual machine, but that’s not speed or battery-friendly.