| ▲ | westurner 18 hours ago | |
"Rethinking Code Refinement: Learning to Judge Code Efficiency" https://news.ycombinator.com/item?id=42097656 eWASM has costed opcodes. The EVM virtual machine has not implemented eWASM. Costed opcodes in WASM for agents could incentivize efficiency re: wasm-bpf and eWASM and the BPF verifier: https://news.ycombinator.com/item?id=42092120 ewasm docs > Gas Costs > "Gas costs of individual instructions" https://ewasm.readthedocs.io/en/mkdocs/determining_wasm_gas_... Browser tabs could show CPU, RAM, GPU utilization; From "The Risks of WebAssembly" (2022) https://news.ycombinator.com/item?id=32765865 : > 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. Presumably workerd supports resource quotas somehow? From 2024 re: Process isolation in browsers : https://news.ycombinator.com/item?id=40861851 : > From "WebGPU is now available on Android" [...] (2022) : >> What are some ideas for UI Visual Affordances to solve for bad UX due to slow browser tabs and extensions? >> UBY: Browsers: Strobe the tab or extension button when it's beyond (configurable) resource usage thresholds >> UBY: Browsers: Vary the {color, size, fill} of the tabs according to their relative resource utilization | ||