20 years ago I was running untrusted code in isolated environments via application containers like HP-UX Vault and later Java Application Servers.
On top of that, Microsoft enganged with the language community so that there were about 20 other languages available for .NET 1.0 on release date.
Here, diggging through the archives,
https://docs.microsoft.com/en-us/archive/msdn-magazine/2002/...
> One of the exciting things in Visual Studio .NET is its language agnosticism. If a vendor has written a .NET-compliant language, you can use it in Visual Studio .NET. It'll work just as well as C# or C++ or Visual Basic. This isn't just a future feature-in-planning. There are already nearly two dozen languages being developed for Visual Studio .NET: Visual Basic, C#, C++, JScript, APL, Cobol, Eiffel, Fortran, Pascal, Perl, Python, RPG, Smalltalk, Oberon, Component Pascal, Haskell/Mondrian, Scheme, Mercury, Alice, and even the Java language.
Naturally MSIL had to support all of them.
The dynamic runtime came later as side effect from IronPython and IronRuby efforts.
Naturally WebAssembly folks are going to tell you they are the very first of this kind of efforts.
Webassembly was designed for sandboxing untrusted code in a webbrowser, giving native like performance and limited functionality.
It just so happened the same characteristics for running untrusted code in the browser work really well for usecases people use AWS Lambda for etc. You have small lightweight applications that have limited system access you need to binpack and have fast startup / low overhead.
Webassembly/WASI isn't replacing the JVM/.NET, it's providing an alternative for specific use cases, running untrusted code in isolated environments that is fast and light weight.