[xky]

We evaluated a few options and settled on Blazor after tiring of the build chain and dependency complexity of the TypeScript world. So far, it’s been nothing but a breath of fresh air to work with.

It’s important to clarify which model you’re working with when discussing Blazor. A lot of complaints seem to stem from using the Blazor server websocket model outside of its specific use cases. The web assembly and prerendered models are more comparable to modern developments in other ecosystems.

[yungporko]

i'm currently working on a large blazor project, and it's pretty much been the same experience as all other shitty microsoft frameworks i've used, where its super nice to work with at first when there isn't too much complexity or edge cases, and all the magic under the hood makes everything super convenient and you find yourself asking why everyone doesn't use this for everything, but by the time the application is too big to consider scrapping it or rewriting it with different technologies, the cracks start to show and it's so much work to even develop the rest of it that you start looking for another job

[bouke]

So what are the cracks that have started to show that have made you start looking for another job?