4 ms·

Maybe I'll use it one day, but I'm extremely skeptical of anything WASM-related. Anyone actually using Blazor in production? How's the effective performance/re

Maybe I'll use it one day, but I'm extremely skeptical of anything WASM-related. Anyone actually using Blazor in production? How's the effective performance/responsiveness? Are the loading times reasonable? Is this usable on low end and mobile?

andybak 3y ago
I think the article is making the case you probably want to hear :)
keltex 3y ago
There are new operating modes for Blazor in .Net 8 that don't require Web Assembly. There's the new "Static server" and "interactive server" that don't require WASM.
bob1029 3y ago
I wrote about Blazor server-side mode yesterday: https://news.ycombinator.com/item?id=38363704 https://news.ycombinator.com/item?id=38363704 I wouldn't touch the WASM mode with a 50 foot fiberglass pole. For me, Blazor was a great entry point. I still use .NET for everything, but now we mostly use simple form posting with string interpolated vanilla HTML responses directly to HttpContext. There are no more frameworks in our shop, but I don't think we could have arrived at this point without things like Blazor, Angular, RiotJs, et. al. temporarily bearing the load of our ignorance until we (or the technology standards themselves) could finally pass through. The web in 2023 isn't like the web in 2017. I think you could start completely blank on vanilla MDN and PHP-style web dev and arrive at an extremely happy outcome. No blazor, no react, node, nothing. Confidence that the javascript or CSS will "just work" 99.99% of the time is there for me now. Avoiding premature optimization regarding UX edges (i.e. justification for SPA) and backend technologies are the major remaining challenges. Chasing a pixel-perfect, cross-platform UX is how you wind up with absolutely nothing to show for it at the end of the day. I blew about a year of my life on that one.
- pkphilip 3y ago
  All true, dear sir. "I think you could start completely blank on vanilla MDN and PHP-style web dev and arrive at an extremely happy outcome." Yep

andybak 3y ago

I think the article is making the case you probably want to hear :)

keltex 3y ago

There are new operating modes for Blazor in .Net 8 that don't require Web Assembly. There's the new "Static server" and "interactive server" that don't require WASM.

bob1029 3y ago

I wrote about Blazor server-side mode yesterday: https://news.ycombinator.com/item?id=38363704 https://news.ycombinator.com/item?id=38363704 I wouldn't touch the WASM mode with a 50 foot fiberglass pole. For me, Blazor was a great entry point. I still use .NET for everything, but now we mostly use simple form posting with string interpolated vanilla HTML responses directly to HttpContext. There are no more frameworks in our shop, but I don't think we could have arrived at this point without things like Blazor, Angular, RiotJs, et. al. temporarily bearing the load of our ignorance until we (or the technology standards themselves) could finally pass through. The web in 2023 isn't like the web in 2017. I think you could start completely blank on vanilla MDN and PHP-style web dev and arrive at an extremely happy outcome. No blazor, no react, node, nothing. Confidence that the javascript or CSS will "just work" 99.99% of the time is there for me now. Avoiding premature optimization regarding UX edges (i.e. justification for SPA) and backend technologies are the major remaining challenges. Chasing a pixel-perfect, cross-platform UX is how you wind up with absolutely nothing to show for it at the end of the day. I blew about a year of my life on that one.

pkphilip 3y ago
All true, dear sir. "I think you could start completely blank on vanilla MDN and PHP-style web dev and arrive at an extremely happy outcome." Yep