I mean, hardly anyone complaining about Java does so because of JVM bytecode.
I'm not sure, where the wasm hate is coming from.
It all comes from OP.
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.
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.
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.
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.
but its not really intended for normal webpages
But I really want to make full stack web apps with rust!
https://www.arewewebyet.org/topics/frameworks/#pkg-actix-web
The main difference is that WASM is an agnostic bytecode without a gc while the jvm is opinionated in a java way. It has a gc, focus on dynamic dispatch and it has knowledge of concepts like exceptions, classes and visibility.
All this leaking of abstractions means languages like java and kotlin are well suited, scala has hit problems and c couldn't be compiled to java bytecode.
Java is disliked because it’s designed around flawed OOP principles developed in the 80s and 90s. The code easily turn into a mess if you adhere to these principles, because they’re flawed. If you avoid using these principles, you will still get a mess, because that’s not how Java is supposed to be used.
Java was such a fractal of stupid design choices in its early years, and a lot of it is still there. OOP except when it's not (int vs Integer, [] arrays but also List et al), no unsigned number types, initially no way to do closures or pass methods around so everything had to be wrapped in super verbose bullshit, initially absolutely dogshit multiparadigm support and very noun-oriented, initally no generics either meaning everything's an Object, when it did get generics they had to do type erasure for backwards compatibility, etc etc etc
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.
Oh yeah how did I forget the billion dollar mistake, definitely one of the worst misfeatures of Java
I think having null is great in some cases where you need to represent missing value. It’s just that there’s no good way to know for sure if you need to do null checks or not. The only way around it is to do null checks everywhere, which no one wants to do because fuck that. Nowadays there’s Optional which solves some of this, but it was introduced way too late.
If I were to redesign Java the first thing I would do is to add a nullable keyword or something.
I think having null is great in some cases where you need to represent missing value.
Option types or sum types would probably be a much less terrible choice for this, although I guess some sort of nullable keyword counts as a sum type
Well, anything that can be captured at compile time or by the IDE is infinitely better than the situation we have today.
Regarding erasure, this is a good read. https://cr.openjdk.org/~briangoetz/valhalla/erasure.html
Great article, thanks for the link! It makes good points that I hadn't really considered; I've probably just been cranky about it because I've preferred heterogenous translations
Glad you liked it!
There is an XKCD for that. Replace "standards" with "programming languages".
WASM = WebAssembly,
this has nothing to do with Java,
but with JS (JavaScript).
JS works with JIT (Just In Time) compilation, meaning every user that requests a web page, will request the JS and your browser will compile that JS on the fly as you request it.
WASM on the other hand is pre-compiled once, by the developer, when he/she is making the code. So when a user requests a WASM binary, they don't have to wait for JIT compilation, since it was already pre-compiled by the developer.
They only have to wait for a tiny piece of JS,
which is still JIT compiled,
a tiny piece of JS to load in the WASM binary.
This saves the user from waiting on JIT compilation and thus speeds up requesting web pages.
WASM also increases security,
since binaries are harder to reverse engineer then plain text JS.
Due to those reasons,
I believe WASM will be the future for Web development.
No clue why people are hating on WASM,
but I guess they just don't grasp all of the above yet.
Having read a significant portion of the base WASM spec, it's really quite a beautiful format. It's well designed, clear, and very agnostic.
I particularly like how sectioned it is, which allows different functions to be preloaded/parsed/whatever independently.
It's not perfect by any means; I personally find it has too many instructions, and the block-based control flow is... strange. But it fills a great niche as a standard low-level isolated programming layer.
WASM is great and as it becomes more accessible it will likely take over more and more
OPs meme is just a sign of someone not understanding the softer parts around development. The meme also seems to forget that we tried java in the browser for two decades and it was just... Horrible from all perspectives, in all layers
I want webpages to be open source, not compiled. That's why I dislike WASM
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.
The problem with java is the language and how it works itself, and not the byte code idea.
I say that as a few things do that and .net, java and wasm are the first that jump to mind.
Hell, pure technically any programming language that is not asm does that :')
My problem is java itself, not its byte code. Wasm as advantage, imo, is that its not stuck to a single language like java is. .net blazor can build to wasm, but you could also use c++ to compile wasm applications :)
haha java is terrible, mostly because of who owns it.
No, Java was always a creeping horror. The VM is one of its less bad features.
Yes it has been steadily getting worse, though.
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.
I'll be chilling over in PHP. Let me know when you're ready for a real language.
You can't compile C to java bytecode, they are fundamentally incompatible. But you can compile C to wasm, which is what you want for a good universal bytecode. Java is shit.
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.
