It probably won’t get rid of js’s dominance, but it’ll give people options. I already see some front end python and rust frameworks thanks to wasm. But for some reason I really don’t like the idea of writing html / css in my rust. But I don’t like the idea of html / css in my rust.

Interesting, yeah. I inherited a Blazor project though and have nothing positive to say about it really. Some of it is probably implementation, but it’s a shining example of how much better it is to choose the right tool for the job, rather than reinventing the wheel. For a while I was joking about setting the whole project “ablazor” until we finally decided to go back to a React/C# ASP.NET stack. If you’re thinking of using Blazor still, though, I think two fun things to look into are “linting issues with Blazor” and “Blazor slow”. I’ve heard people praise it, but they tend to be those who consider themselves backend devs that occasionally get stuck making frontends.

What, you can write a website in C# and have It output as a website using wasm? I have never touched wasm. That might be an interesting way to try it though.

Which is functionally identical to the last one you posted. Are you just doing the same joke in every format you can? Fuck the internet sucks now.

Of course, technically you can compile anything to almost anything. But I don’t think linking to a project that’s unmaintained for 15 years really helps your argument.

Also: everything is nullable. There are no safety guarantees to ensure you’ve done the necessary null checks. And if you miss your program will crash.

Regarding erasure, this is a good read. https://cr.openjdk.org/~briangoetz/valhalla/erasure.html

Java bytecode is designed specifically for class-oriented languages like Java and works terribly with anything else.

Why would they? WASM is Web-Assembly, so Assembly is a lower level language than Java.

You can use C# WASM through Blazor, and Java WASM though JWebAssembly. WASM as core is supposed to be language agnostic. So If you want a JVM in WASM you can build it on top of it

WASM projects can be open source,
just like Android apps can be.

However in both instances the compiled versions of it are not easily readable.

Also you can validate binaries against a shasum to ensure no tampering has happened with them.

Yes

Please do say more because I don’t think the argument you’re trying to make is coming across clearly. Obviously your intelligence is at a level far higher than us low-iq plebs, and we need your brilliant mastery of these topics to be poetically spelled out for us. For we are not worthy otherwise.

less bad

Hum, no. The idea of a fast intermediate representation that is still high-level enough to allow for runtime optimizations and portability is GREAT. It’s not “less bad”.

But, of course, everything else destroys the language. A language agnostic WASM is taking that one really great part, and dropping everything else.

Sun Microsystems was once the great hope of the computing world, and technically the JVM was first to normalise the use of VM’s, albeit from a containerised perspective. It was Docker before docker, in some sense.

This coupled with Solaris and the SPARC systems that were Java-native (whatever that means) enabled this type of containerisation from a hardware level, which again: was a huge thing.

But, Sun turned for the worse once the JVM hit browsers and server stacks. That’s when their SaaS model was envisioned, that was the precursor to the acquisition by Oracle.

So it started nicely, but hit the enshitification velocity somewhere in the early 2000s.

Join the player haters ball

Have you seen what it outputs? The same way we can compile C to brainfuck, it doesn’t mean it’s good or is useful.