That's a fair reason. It's important to realize how often we re-invent the wheel in our field. As an example, you're an expert in distributed systems, which I've only recently started dabbling in. In the process I'm learning how so many of the fancy "new" distributed systems and we have today were essentially invented decades ago.

But in the WASM case, to what end? There's a cost to your comments. I'm sharing an example of how WASM has helped me solve a real problem, and might solve real problems for other people. Your comments create noise to these types of discussions.

Maybe it's worth the tradeoff in your mind, but I'm curious what your end goal is?

WASM is designed to be embedded and its model is that of native code rather than any particular high-level language's primitives. It is closer to LLVM than Java. Comparisons to Java are surface-level and boring, since all foundational reasons why Java failed are false of WASM.

Believe it or not, just because on an abstract technically something similar has been done before, its possible for people to still care about something that is being built. Reinventing the wheel is perfectly fine and even good, special if it happens in a different context and with a different community and process. And the WebAssembly people are well aware that Java/CLI exist and are learning from it.

Making the same comment on every single Webassembly thread for the last couple years as if the everybody working on WebAssembly or WASI is some bro-programer born in 2008 is just disrespectful to the engineers working on these projects.

Sorry that we are not all as cool as you and use UNCOL everyday. I mean who would want to use a technical idea that isn't first of its kind.