this post was submitted on 05 Apr 2024
114 points (73.4% liked)

Programmer Humor

19723 readers
83 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 

Let's reinvent java bytecode but... different

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 74 points 7 months ago (7 children)

Do you really think the reason people hate Java is because it uses an intermediate bytecode? There's plenty of reasons to hate Java, but that's not one of them.

.NET languages use intermediate bytecode and everyone's fine with it.

Any complaints about Java being an intermediate language are due to the fact that the JVM is a poorly implemented dumpster fire. It's had more major vulnerabilities than effing Adobe Flash, and runs like molasses while chewing up more memory than effing Chrome. It's not what they did, it's that they did it badly.

And WASM will absolutely never replace normal JS in the browser. It's a completely different use case. It's awesome and has a great niche, but it's not really intended for normal web page management use cases.

[–] [email protected] 9 points 7 months ago (3 children)

And WASM will absolutely never replace normal JS in the browser. It's a completely different use case. It's awesome and has a great niche, but it's not really intended for normal web page management use cases.

While I overall agree that JS / TS isn't likely to be replaced, Microsoft's Blazor project is interesting conceptually .... Write C# webpages and have it compile down to WASM for more performance than JS could offer.

[–] lambda 1 points 7 months ago (1 children)

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.

[–] [email protected] 3 points 7 months ago

The problem with blazor as I understand it, is that no, it does not compile your C# into WASM. Instead, it compiles into a standard .net module -- with as much excising of unused code as possible -- and distributes it with a CLR that is compiled to WASM. So effectively you're running the .net VM inside the WASM VM. If you do client-side blazor, which is not even MS's push anymore because they stand to make more money if you write server-side blazor and deploy it to Azure.

Do look it up yourself tho. I could have a totally wrong understanding. I haven't looked into it in some time because I've not been in a position to start a new frontend project from scratch. I would love to do my frontend stuff in C# though, don't get me wrong.

load more comments (1 replies)
load more comments (4 replies)