3 ms·

Frankly, having lived and upgraded many projects through asp web forms, wpf, silverlight, and razor, I've decided "never trust .NET UI libraries to survive". So

Frankly, having lived and upgraded many projects through asp web forms, wpf, silverlight, and razor, I've decided "never trust .NET UI libraries to survive". So I'm avoiding Blazor entirely and just sticking with the react ecosystem. I trust that 100x more than I trust Blazor, partly because the ecosystem and user base is 100x larger. I won't be the slightest bit surprised to see Blazor tossed in the trash in three years, but I'll eat my hat if react is gone by then. Sure, maybe it's popularity will wane for some other similar library, in which case I'll switch to that. But I'm sticking with the beaten path on the front end.

cjk2 2y ago
Ha we still have all of those (apart from Silverlight) in production. A number of years ago I had to get an overexcited architect to not rewrite everything in Silverlight. Front end .Net is a shit show. You are right to stay the hell away from it.
mythz 2y ago
You've got good reasons for not trusting any .NET GUI libraries from Microsoft, I don't either since they all ultimately end up abandoned however that doesn't definitely doesn't apply to their premier Server frameworks which enjoys first class long lasting support. Razor didn't go anywhere, it's still the predominant language .NET Server HTML Views is written in since its release in 2010, whether it's in MVC, Razor Pages or even Blazor which enjoys the same familiar statically-typed syntax with great tooling and high performance compiled views. There's no chance that's going to happen with Blazor, which has become the future of .NET Web App development, it's a unique technology that's highly versatile whose multiple rendering options supports a wide number of different use-cases that's enjoyed by most of .NET developers. Personally I think it's a fresh of breath air after several years of fragile npm SPA development with broken upgrades stemming from its 100s of deps of varying quality and uncoordinated releases. All I liked from SPAs is its fast navigation, but we also get that from Blazor's Enhanced navigation without SPA complexity, heavy client state, maintaining client side routing, poor SEO, large complex builds, etc.
- JackMorgan 2y ago
  It's a bold claim to say that the team that produced a half dozen failures in a row has "no chance" of producing another failure. I will set a calendar reminder for five years "is Blazor still around" and I'm pretty confident the result will be "well yes but it's terrible for these reasons, but this new library Tazor is the future of .NET web UI and it's not going anywhere!"
  - mythz 2y ago
    That's not all from the same team, Microsoft is a 2T company with software in every industry. Their GUI suffered through lack of investment and neglect. Their Web Server frameworks are producing software running on their cloud, Windows servers and infrastructure products like SQL Server, all enjoying multi-billion dollar businesses. Extrapolating abandonment of Windows GUI software with poor business models, with cross-platform libraries running on growing revenue centers is foley, I'll happily take any "5 year Blazor" bet.
  - switch007 2y ago
    "Tazor", ohh! I appreciate a good swipe at their intense fetish of confusing naming

cjk2 2y ago

Ha we still have all of those (apart from Silverlight) in production. A number of years ago I had to get an overexcited architect to not rewrite everything in Silverlight. Front end .Net is a shit show. You are right to stay the hell away from it.

mythz 2y ago

You've got good reasons for not trusting any .NET GUI libraries from Microsoft, I don't either since they all ultimately end up abandoned however that doesn't definitely doesn't apply to their premier Server frameworks which enjoys first class long lasting support. Razor didn't go anywhere, it's still the predominant language .NET Server HTML Views is written in since its release in 2010, whether it's in MVC, Razor Pages or even Blazor which enjoys the same familiar statically-typed syntax with great tooling and high performance compiled views. There's no chance that's going to happen with Blazor, which has become the future of .NET Web App development, it's a unique technology that's highly versatile whose multiple rendering options supports a wide number of different use-cases that's enjoyed by most of .NET developers. Personally I think it's a fresh of breath air after several years of fragile npm SPA development with broken upgrades stemming from its 100s of deps of varying quality and uncoordinated releases. All I liked from SPAs is its fast navigation, but we also get that from Blazor's Enhanced navigation without SPA complexity, heavy client state, maintaining client side routing, poor SEO, large complex builds, etc.

JackMorgan 2y ago
It's a bold claim to say that the team that produced a half dozen failures in a row has "no chance" of producing another failure. I will set a calendar reminder for five years "is Blazor still around" and I'm pretty confident the result will be "well yes but it's terrible for these reasons, but this new library Tazor is the future of .NET web UI and it's not going anywhere!"
- mythz 2y ago
  That's not all from the same team, Microsoft is a 2T company with software in every industry. Their GUI suffered through lack of investment and neglect. Their Web Server frameworks are producing software running on their cloud, Windows servers and infrastructure products like SQL Server, all enjoying multi-billion dollar businesses. Extrapolating abandonment of Windows GUI software with poor business models, with cross-platform libraries running on growing revenue centers is foley, I'll happily take any "5 year Blazor" bet.
- switch007 2y ago
  "Tazor", ohh! I appreciate a good swipe at their intense fetish of confusing naming