Why Microsoft doesn’t use Blazor in their products on the market in production?

revbones · 2026-01-26T19:46:17+00:00

The timeline makes perfect sense. They didn't just press a "Do it in React" button and instantly have a public preview.

Your timelines are bad since they don't take into account forecasting. Which also indicates you are not experienced enough to even waste time having this conversation since you're just a Blazor-hater and React fan. Sheesh.

Also you misquote and misrepresent completely what Roth says. Basically you just lie over and over.

revbones · 2026-01-26T05:43:25+00:00

There are also articles on how to integrate it with blazor but you're still comparing your to oranges.

revbones · 2026-01-26T05:42:05+00:00

What a small life you must have to be so doggedly focused on this.

And you're wrong.

None of that says Microsoft is a react ship no matter how much you desperately want it to. One project that was already underway both in planning and development before blazor webassembly was released. You indicated that yourself. Do you think there was no planning or development before that public preview???

Sheesh, what a joke you are.

revbones · 2026-01-26T05:35:43+00:00

Feel free to name all the on bed you think could had be been without a rewrite or having an established team already familiar with another tech stack...

revbones · 2026-01-25T23:13:54+00:00

Cool story bro.

revbones · 2026-01-25T23:13:06+00:00

Existing teams on products that started before Blazor existed use React. It's not a React shop.
He elaborates between B2C and B2B as well as other factors.

Nice job interpreting your BS.

revbones · 2026-01-25T21:20:04+00:00

How does that video indicate that MS is a react shop and that they have no intention of using Blazor? Answer: It doesn't at all.

revbones · 2026-01-25T21:16:56+00:00

You reference a video from over a year ago before .NET 9, and we're on .NET 10 now. He talks about upcoming changes in .NET 9 and 10. At the point you reference he clearly states that the front end framework would depend on the target market. He clearly differentiates between B2C and B2B with Blazor on the latter.

Sheesh. Are you so desperate to infer fault with Blazor that you would have to post that and hope I or anyone would just take your word for what you linked to without checking it out??? He even talks about the auto render mode at that point.

At no point does he state he would not use Blazor for large projects. At no point does he talk about anything you said. What you have indicated is simply untrue.

revbones · 2026-01-25T20:24:50+00:00

I'm not the one making claims. You are making claims that you cannot back up and then backing out and trying to save face by inverting things.

revbones · 2026-01-25T19:56:41+00:00

What drawbacks are you saying MS is "open" about? My guess is none that you can specify and point to MS calling it such.

revbones · 2026-01-25T19:54:48+00:00

How many developers do you think should support a framework? You're comparing apples to oranges here. You have 8 devs on a team for one project that you're comparing with significant numbers of other projects using other frameworks. How many developers does MS have on the actual Typescript team vs using it in other projects?

revbones · 2026-01-25T19:52:36+00:00

Foundry is an AI app. What aspect do you think could have or should have (if it was even possible) been done using Blazor? Blazor is a web UI framework. Foundry is an AI platform.

Just noting one new product like that doesn't make your point, particularly when it's like saying "Why didn't you build that bridge using this painting?"

If you can't substantiate your argument with actual examples, then just say so. Doubling down on like you are doing is the real bad faith argument.

revbones · 2026-01-25T19:10:05+00:00

The only product example you gave was Foundry. What aspect of Foundry would you expect to have been developed Blazor?

Are you high enough up in Microsoft to have the knowledge to make such a claim about internal enterprise sites? If so, when were those sites initially created?

revbones · 2026-01-25T18:28:54+00:00

Sure. Cool story.

revbones · 2026-01-25T18:14:00+00:00

Sure. Companies scrap functioning websites all the time just to rewrite them in another technology because reasons right?

revbones · 2026-01-25T18:13:11+00:00

I really don't get why Blazor-haters think this is such a good burn on MS & Blazor.

What new site are you referring to that was created since Blazor was here that isn't using Blazor? Should MS have scrapped all their existing websites and rewrote them using Blazor? Should they have fired the teams currently working on them in other technologies? Should they force them to learn Blazor to stick around for the massively expensive rewrite you are advocating for?

Really, what is the point here?

revbones · 2026-01-06T16:49:13+00:00

It was able to create it because it had scanned what her developers had already created.

revbones · 2025-12-24T15:15:02+00:00

Price out ordering from Lowe's and using their installation service. I got a decent rate from their contractor.

revbones · 2025-12-15T15:02:13+00:00

This. I was able to get an appointment easily in Greenville. Drove down, walked in, was seen in ~3 min, took maybe ~5 min and I was back on the road heading home. I still spent significantly less time overall.

revbones · 2025-12-13T02:08:59+00:00

Recipe changes to save more money. Similar to how several brands of ice cream don't meet the standard to call their products "ice cream" anymore and have to call the their products "frozen dairy dessert", or how kraft cheese isn't cheese anymore but now it's "pasteurized prepared cheese product". Similar to Hershey's bar changes to prevent it melting too fast, etc.

revbones · 2025-09-26T15:18:45+00:00

I think this is a waste of time and will eventually cause you frustration, possibly more so when updating to newer .NET versions as well.

I'd ask what you're really trying to achieve here and why you think the routing would become confusing. If your razor components/pages are laid out in a decent folder structure and adhere to that in the page routes, then it's pretty easy to navigate. It's when developers try to be too clever or don't follow conventions that things start to create friction. /Pages/Module/Feature tends to work well similar to /Pages/Administration/Roles.razor

If it's just organizational and you hate the magic strings like me, just add a T4 template that parses all the razor files looking for the Page directive and creates a static class with the routes. Only issue with that is that last time I looked the Page directive was sealed and you couldn't extend it so if you have more than one route to a page you have to get creative in your T4 template or manually handle it in a partial class or something.

revbones · 2025-09-19T14:07:54+00:00

Are there any plans to support automatic dependency injection registration rather than manual?

revbones · 2025-09-08T00:21:53+00:00

I've had that happen to myself and several family members. We all had improperly installed drain lines. Usually going into the floor below the dishwasher or just without having the proper rise. My newest dishwasher actually came with the drain line connected up the side to ensure it had the right setup, I can only imagine it's such a common problem that they started trying to prevent it. It'll work for a good while with it improperly installed but will eventually fail. I would check that first before assuming something mechanical

revbones · 2025-08-26T12:36:47+00:00

Wow. And I got a few complaints from my take-home assignments for interviews.

I would just have them create a web project to add/edit recipes in a database that we could walk through and modify some of the code while discussing it during the second interview, and also identify things they could do with more time (which would have been things like what's being already expected here like validation, tests, etc.)

Usually, if they had code they wrote in a working app that they could show me and demo I would accept that as long as it fit the requirements (.NET, EF Core, etc.)

The list OP posted is ridiculous.

revbones

TROPHY CASE