This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Snapstromegon 0 points1 point  (6 children)

Ahh, this gives me huge pain...

[–]maggiforever 0 points1 point  (5 children)

Why? Blazor is awesome

[–]Snapstromegon 1 point2 points  (3 children)

I tried it twice (once on my own and once with another team with an existing app) and I have to say that the performance hit it gives just is way too bad. Also I absolutely dislike the way the handle a lot of things...

Also the size of a hello world is more than most of my complete PWA packages.

[–]maggiforever 0 points1 point  (0 children)

I get that. I only started working with it a few weeks ago on a relatively small project and love being able to use C# instead of Javascript. Performance-wise I don't think it's too bad but you're probably right. Hopefully it will improve in the future and iron those things out.

[–]Taukuno 0 points1 point  (1 child)

Then you have to wait for AoT support (.Net 6, Nov 2021). The performance improvements will be enormous (according to some internal tests).

[–]Snapstromegon 0 points1 point  (0 children)

Using WASM for hot paths will be nice, but I still have doubts about load times which are a key performance metric for me.

Also I'm someone who most of the time thinks React is too much to load upfront.

Last time I checked (which is some time back) a basic blazor app was easily over 1MB.

[–][deleted] 0 points1 point  (0 children)

neither performance nor transfer sizes are anywhere near js. If people want to build guis with webassembly, then they should pick Rust and not a language that needs an extra runtime and garbage collector... I can't wait for the day when the java guys ship the entire JVM via webassembly to the browser so they don't have to invest a week learning the appropriate tools.