3 ms·
I'm afraid that we are on vastly different wavelengths. If you feel that you can improve WebAssembly, then by all means, please do so. I am convinced that I ca
by Yoric 9y ago
I'm afraid that we are on vastly different wavelengths. If you feel that you can improve WebAssembly, then by all means, please do so.
I am convinced that I can do good by making Binary AST a reality, so I will focus my energy on that.
Thanks for the conversation.
- dmitriid 9y agoSo, basically, all your "arguments" for binary AST resolve to: - binary AST will not have versioning problems unlike WASM (this is false) - binary AST is better than ASM, because as soon as you standardize on bytecode, "your VM will not evolve" (this is false) - binary AST can be used to view/debug source code, while WASM can't (this is false) - binary AST is faster to load and parse than WASM (neither false nor true, because there are no comparisons or experiments) - supporting WASm means supporting two versions of ECMA standard unlike binary AST (which is false) and so on and so on However, Javascript is already a dumpster fire, so this effort will neither improve nor worsen the situation