- Joined
- May 4, 2015
webassembly is the first step in making web decent, aka fast. Once it's mature maybe I will look into making web applications. For now though, web uses way too much javascript for my liking. It's ugly and slow, the faster it's out the better.Maybe browsers get strict about executing WebAssembly, it becomes a thing like "Don't enable ActiveX bro!!!". I don't think people really considered miners at the time, and just assumed the fact it's sandboxed like regular JS was enough to avoid abuse. WebAssembly can be disabled without affecting existing JS so it's not like the browser is agnostic when it comes to it: https://github.com/stevespringett/disable-webassembly
There's very few uses of WebAssembly at the moment, games, mostly. If the internet becomes less dependent overall on JavaScript because of miners I'd call that a good thing.
What we need is a ressource monitor for browsers telling you which tab/script is using cpu/memory/sound/bandwidth and kill/restrict the things that use too much. Google saw it, browsers become more and more entire operating systems. Imagine if windows started restricting which program could run based on cpu usage instead of offering the task manager.
Can we please go towards "tools that work" instead of assuming everyone is an idiot this time?