Blazor will produce super bloated web apps. I can see it being used for an in-house thing with captive users but for a real world product or a public app? It would be a terrible choice.
Also the DX is just not there. Hot reload is a mess. Even when it works it's too slow. Once you start using hot reload with Vite you can't go back to waiting seconds for every change and full page reloads.
> Compared to what?
Everything else?
Do you think it's acceptable that it took 4 years for Minimal APIs to get validation?
What about hot reload being broken for years and years?
>Do you think it's acceptable that it took 4 years for Minimal APIs to get validation?
Well thay don't call it Minimal API for nothing. Jokes aside, what stopped you from calling validation yourself explicitly?
>What about hot reload being broken for years and years?
Can't comment on this, because I have never needed it. I can work faster with writing tests, but I guess it's fair to assume there are some who would need it.
> what stopped you from calling validation yourself explicitly?
Error messages. Even with the validation in .NET 10 you can't get the actual JSON property to display in the error message, instead you get the C# property.
FastEndpoints fixes this but uses Fluent so now you need to rely on a couple more dependencies.
Which version worked flawlessly? And I guess blazor can work great but that's super specific to what you use it for. Much more so than most front end technologies/stacks. And both WASM and Server versions have a lot of compromises.
We used Blazor years ago and it worked flawlessly already then. Hard to believe it's worse today. And what's wrong with Identity?
>progress in .NET is super slow
Compared to what?