| I don't program in JavaScript. > Anything you can do in wasm you can do in JavaScript, only was can do it faster. It's faster and more flexible because it can easily be targeted by compilers. That is the problem. This might sound surprising. Allow me use an analogy to explain it. Let's assume some new technology was invented to more easily breed cattle for meat production. I completely understand why some people would want that, and develop it. I think breeding and killing cows and bulls just to eat a steak is unethical. So, I would absolutely refuse to work on the technology, and I'd expect the same of everybody that cares about being ethical. Now, coming back to JavaScript and wasm, it is used to deploy code in a way that takes the control of the software from the users to the developers. The deployed code is unreviewed, unaccounted, unsigned and executed automatically. I consider unsafe in the computing sense. So, I consider code execution on the web unacceptable. Since, wasm makes that easier and more efficient, I'm opposed to it. On top of that I consider JavaScript a bad language. I'm worried by how much it's pushed as a teaching language. |
I can see where you are getting confused. It is actually just faster. Again, there is nothing you can do is wasm that you can't already do it javascript.
> The deployed code is unreviewed, unaccounted, unsigned and executed automatically. I consider unsafe in the computing sense. So, I consider code execution on the web unacceptable.
All of these things apply to javascript.
> On top of that I consider JavaScript a bad language. I'm worried by how much it's pushed as a teaching language.
This has absolutely nothing to do with anything in this thread. It is pretty clear that you have biases and frustrations that have nothing to do with technical merits.