Let's reinvent java bytecode but... different
this post was submitted on 05 Apr 2024
114 points (73.4% liked)
Programmer Humor
19585 readers
517 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.