design

Don't there need to be per- CPU/RAM/GPU quotas per WASM scope/tab? Or is preventing DOS with WASM out of scope for browsers? IIRC, it's possible to check resource utilization in e.g. a browser Task Manager, but there's no way to do `nice` or `docker --cpu-quota` or `systemd-nspawn --cpu-affinity` to prevent one or more WASM tabs from DOS'ing a workstation with non-costed operations. FWIU, e.g. eWASM has opcode costs in particles/gas: https://github.com/ewasm/design/blob/master/determining_wasm...

FWIW, Ethereum WASM (ewasm) has a cost (in "particles" ("gas")) for each WebAssembly opcode. [1] Opcode costs help to incentivize efficient code. ewasm/design /README.md [2] links to the complete WebAssembly instruction set. [3] [1] https://ewasm.readthedocs.io/en/mkdocs/determining_wasm_gas_... [2] https://github.com/ewasm/design/blob/master/README.md [3] https://webassembly.github.io/spec/core/appendix/index-instr...

PL people often direct their "it should be functional and use strong typing" critique at the EVM rather than Solidity. Solidity is just one HLL (higher level language) that compiles to EVM bytecode. A lot of the limitations of Solidity are due to constraints of the EVM, but the EVM is evolving. For instance, the next planned hard fork will enable the EVM to pass dynamically sized data (e.g. solidity arrays or strings) between call stacks. Previously arrays had to be fixed-size, so you'd have to define a fixed maximum size, then always return data of that size (usually a lot of empty elements). This feature, like many others, is somewhat challenging to design because every execution step of the EVM must be metered by a "gas fee"; the first version of the EVM kept it simple by only allowing return data to be a fixed size. See these issues f

One issue is that not even the devs[1] working on these challenges dare to make claims like "2x scaling". Because it's a ridiculous statement since "scaling" is not just TPS and it's a more complicated topic. The developers are still on design phase, they never said anything about #x'ing the TPS or anything. It's really unfortunate that Ehrsam made such a horrible post. I'd rather have Vitalik or Vlad making a State of Scaling blog post than this propaganda to circulate among newcomers so they can support the price. [1]: https://github.com/ewasm/design