The Breakpoint Show@rafaelldi This is just my opinion ( @cwoodruff), but I find that dotnet is a great general framework, but I find it strongest for backend work myself. I think dotnet could have a resurgence on the web front end by having a simpler path for 90% of the needed work for web dev. Maybe @maartenballiauw and @khalidabuhakmeh have their own takes.
Maarten Balliauw@breakpointshow @rafaelldi @cwoodruff @khalidabuhakmeh Maybe we should make this a topic in a future episode?
Chris Woody Woodruff
Rocky Lhotka 🤘🖖@cwoodruff @maartenballiauw @breakpointshow @rafaelldi @khalidabuhakmeh Personally, I think #blazor is finally an answer to #dotnet having a decent UI framework. The productivity of VB6 with the reach of the web.
Khalid âš¡@rockylhotka @cwoodruff @maartenballiauw @breakpointshow @rafaelldi I have mixed feelings on Blazor. I can see why devs would leap at it, but the user experience can suffer because of web sockets or Wasm payloads.
Blazor United also feels like a step down from what Razor already offers. No Tag Helpers is a big missing feature.
Blazor development seems to have sucked the oxygen out of the rest of the ASP.NET framework ecosystem.
@rockylhotka @cwoodruff @maartenballiauw @breakpointshow @rafaelldi I'm watching @[email protected], he's my Blazor canary in the coal mine.
@khalidabuhakmeh @cwoodruff @maartenballiauw @breakpointshow @rafaelldi In my mind it a difference between (what I think of) as a web site experience vs an app experience.
#blazor hasn't been good for a web site experience compared to razor pages.
It's good for an app experience. I'd much prefer to build a call center app or order entry or other line of business scenarios with Blazor compared to razor pages.
And in most of those scenarios, seconds of app load each morning is irrelevant.
@rockylhotka @cwoodruff @maartenballiauw @breakpointshow @rafaelldi that's fair, and applying the tech matters for folks. Each team should evaluate it based on their needs. That said the hype-chamber can be strong in our ecosystem so it's hard to get an unbiased view of solutions sometimes.
Damselfly - Photo Management 📷@rockylhotka @khalidabuhakmeh @cwoodruff @maartenballiauw @breakpointshow @rafaelldi this, 100%. Building a public site with blazor isn't optimal. Building an internal distributed scalable app like Damselfly (or the fintech business app I'm building with Blazor at work) it's perfect. Great DevX, good UX and in prod, across a LAN the startup is unnoticeable.
@khalidabuhakmeh @cwoodruff @maartenballiauw @breakpointshow @rafaelldi It will be interesting to see if the web socket issues are largely resolved in #dotnet 8 with the new #signalr features.
Philip Doherty 🖖@rockylhotka @khalidabuhakmeh @cwoodruff @maartenballiauw @breakpointshow @rafaelldi What are the websocket issues? Currently building out a complex product with Blazor as the stack.
@phildoherty @rockylhotka @cwoodruff @maartenballiauw @breakpointshow @rafaelldi web sockets are hard and can have connectivity issues.
.NET 8 is adding more resiliency and reconnect options.
Also, WebSocket sessions need to be managed in-memory on a server, so prepare your production environment accordingly.
@khalidabuhakmeh @rockylhotka @cwoodruff @maartenballiauw @breakpointshow @rafaelldi Thanks, ready for all that. Was wondering if there was more. The productivity in Blazor is off the charts so I've got a lot of time for it, and extra time.