News for hackers. Stuff that matters.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by throwaway894345 on Tuesday May 30, 2023 @12:41PM (#36127038)
The JVM expects that languages will conform to its bytecode specification, which is designed first and foremost for Java. WASM's bytecode specification is designed to support the existing ecosystem of languages including Rust, C, C++, Go, etc which can't easily target the JVM. Relatedly, the body which manages the JVM specification is comprised of major Java vendors and users; they don't represent developers of other languages even if the JVM nominally supports a few of them.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by kgeist on Tuesday May 30, 2023 @01:39PM (#36127891)
Microsoft's NET allowed you to compile C++ to pure CIL (.NET's bytecode) and run it inside a VM since the early 2000's. It wasn't very popular so it was deprecated.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by TUSF on Tuesday May 30, 2023 @03:28PM (#36129408)
> Microsoft's .NET

There's your problem.

Sure, .NET is technically cross-platform, but that's a relatively recent development, and WASM has runtimes that let it run in most environments, even microcontrollers.

Also, looks like C++/CLI had conflicting syntax with standard C++, so it might not have worked on some applications without some patches.