Holy shit How is it so fast? Runs shit instantly
>>102637841It's just bytecode designed to run decently on most common architectures being run through an interpreter.Like flash, but semi decent.
>>102637841All that compute and yet /g/s hands can never build anything
>>102639565>Like flashwrong, WASM can't do any graphic without having to go through JS. They should have made wasm as a new way to interact with the browser without having to go through JS.
>>102640578Isn't that where WASI comes in, whenever thats done?
>>102640627I dont know about WASI. If they make it that the wasm vm has access to the same browser functions that is exposed to the JS vm, that would be great. Right now you need something like enscripten and the like to generate all that glue code for you because otherwise it's a fucking pain to do. I really think that if the W3C did that from the get go the wasm adoption rate would be high.>t. wrote a "lisp" interpreter in webassembly text format (WAT) for "fun".
Wasm is for NIGGERSWasm is for NIGGERSWasm is for NIGGERSWasm is for NӏGGERS
>>102637841It's not a scripting language?
because it's a vm that only enforces stuff like memory bounds checking. it maps well to most every CPU.IMO the amount of shit you need for it seems memey when you could probably get away with stuff like https://rlbox.dev/ instead, which ironically uses wasm to get guaranteed correctness.
>>102640627That is not what WASI is.
>>102637841>modern garbage>fastyeah sure buddy
