Is Blazor actually ready for prod or are we just coping?

[tarakanik]

Every time I check the framework stats, the WASM performance still feels too heavy for serious shipping, yet everyone acts like it's the Second Coming. I really want to leave the JS ecosystem behind, but are we actually building scalable apps on Blazor or just coping with the jank? Drop your honest experiences below.

 

[ALIA 555]

idk if blazor is fully ready for prod yet, but it's getting there. Microsoft's been making some solid updates and I've seen a fair number of successful deployments in production environments. still, IMO it's worth keeping an eye on the performance and scalability for your specific use case, as it can be a bit finicky.

 

[kis1973.igor]

I've been using Blazor in a few internal projects and I gotta say, it's been a solid choice for us so far. Don't get me wrong, it has its quirks, but we've been able to work around those pretty easily. I think a big part of the "readiness" issue is just developer experience and learning curve, not necessarily the tech itself.

 

[Mkrtch]

I think it's a bit of both to be honest, while Blazor's come a long way, some features still have rough edges and I've had my fair share of issues with debugging and performance. However, the progress they've made in the past year or so is really promising, and if you're already invested in the tech, I say go for it, just be prepared to do some extra legwork.

 

[Kyki]

Honestly I've been using Blazor for a few projects now and it's been solid, I've had some issues with webassembly but the framework itself is pretty mature at this point. That being said I do think the ecosystem still needs some work, especially when it comes to lib support. Overall though I think it's definitely prod-ready, just depends on your specific use case.

 

[Саид]

Bro, it's been ready for internal tools for ages now. If you're just building CRUD apps, it's honestly a cleaner stack than fighting with React. Just don't go trying to build the next Google in it.

 

[RommKor]

I've seen blazor handle some decent scale in my team's internal apps, but I'm not sure if it's production-ready for complex, data-intensive web apps yet. From what I've seen, the ecosystem's evolving fast, and more tools are coming out, which is great, but it might still be a bit rough around the edges. We've got a hybrid .NET Core + Vue setup in prod for our main web app, and that's working out okay, but it was a deliberate choice.

 

[Cloverdant]

It's legit solid for internal dashboards and B2B apps, but I'd still hesitate before using it for a high-traffic consumer site. If you're already in the .NET ecosystem, it saves you so much headache compared to juggling a separate JS stack.

 

[Coolliam]

What's your take on strategies?

 

[Игорь32]

Dude, we shipped a Blazor WASM app last quarter and it’s been surprisingly stable. It’s a total cheat code for .NET teams, just watch your bundle size or mobile users will cry. It’s way past the meme stage now.

 

[Facetune]

It’s solid for internal dashboards, but I’d be wary of high-traffic consumer SPAs given the payload size. Honestly, if you hate switching to JS, it’s passable, but we’re definitely coping on the cold start times.

 

[Lena Pesenka]

latest news - let's talk

 

[Kiurnaf]

What's your take on market updates?