[otabdeveloper2]

The JVM and CLR suck balls.

They put in huge amounts of effort into things that don't need solving, and the things that need to be solved they do in the most roundabout way possible.

What we _really_ need is a sandboxed VM for running C code securely and efficiently.

The JVM is pretty much the opposite of that; it's not sandboxed, not secure and certainly not efficient as a target for C code.

We're hoping WASM starts over from scratch and does things right this time around.

[Teknoman117]

... 20 years later

JVM, CLR, and WASM suck balls. People have been breaking the sandbox for the better part of a decade.

We're hoping Cool New Thing™ starts over from scratch and does things right this time around.

[timClicks]

But isn't that the point? We should be getting better at building software over time. Sometimes that means restarting.

[Hydraulix989]

UNIX is a good counter-argument.

[JeremyBanks]

UNIX is thoroughly obsolete. Its continued use is from inetia; people rarely need anything but a tiny subset of its capabilities, for which there are more simpler alternatives every day.

[maccio92]

are you kidding? do you know how many subsystems that people take for granted are using UNIX? furthermore, how do you get simpler than UNIX? it's not complex..

[Hydraulix989]

I just didn't feel like responding since it was clear OP didn't know what he was talking about.

[vbuwivbiu]

"it's not sandboxed" well, it is, and it's secure and it can run bytecode as fast as C

[saagarjha]

Both of those claims need qualification: it’s not quite secure, and it’s not quite as fast as C.

[AnIdiotOnTheNet]

This time, things will be different!

I mean, maybe they really will be, but history suggests otherwise.

[antpls]

Isn't sandboxing solved at the host OS level ?

Android apps are sandboxed Java apps.

Containers turn almost any Linux process into a sandboxed process.

Am I wrong ?

[specialist]

What would a sandbox for C (native code) look like?