@alexzeitler It’s pretty decent. My difficulty with it might be it’s doing too much abstraction, which limits what you can do with Alpine JS. (Think confirmation before submitting an event).
@zachleat I never used to have a case until I was in Mexico, placed my phone on a table, and it slid off and landed flat screen-first onto a tile floor.
Oh man oh dang I just figured out how to do something really hard and my code worked the first time and the hell do you MEAN 27 errors come here I'll show you 27 errors #godot#godotengine#indiedev#gamedev
The great tragedy of #aspnetcore is that it probably would have wider adoption if it stayed the course with MVC and Razor pages now that SSR is the latest trend.
The cycle returned to ASP.NET's strength, and Blazor had to pivot back to SSR to keep up.
Instead of being ahead of the curve, it's now behind it. 🤷♂️
@lostprototype Yeah, Laravel is surprisingly robust and the ecosystem is pretty solid. I was looking at a colleagues PHP framework the other day and it was really readable and MVC-like. I think the switch wouldn’t be too bad (especially with PhpStorm and JetBrains tooling ;) )
@TheJoeFin Calling it Blazor Server was likely a marketing “mistake” since it used WebSockets, which ties clients to the server. That’s why it’s called Blazor Interactive now. 😀
This is the usage statistics after 6+ years of release (2018 for Blazor).
@TheJoeFin I also meant it’s behind what ASP.NET MVC could do regarding functionality.
The paradigm shifts in Blazor required refactoring parts of ASP.NET Core to provide that functionality to Blazor. So, even the version of Blazor today still lacks some features you have when using a different approach.