Why I'm Worried About Blazor and its Future

Hello, everybody. I'm Nick, and in this video, I will react to a 4-year-old video of mine that has been unlisted 3 hours after it was published because of backlash. Let's see if I was right.

Don't forget to comment, like and subscribe :)

Social Media:

#csharp #dotnet

[jonathanblackwell]

We use blazor in production and chose it specifically because our team gets many varying assignments. For maintenance, being able to go back 6 months or a year later and not have to relearn a language we haven't used since is a big win for us.

[Fear]

I’m a developer in a small team within a large company, primarily focused on building internal-use applications. We mostly work with C#. We’re slowly migrating older apps to web technologies. Initially, we started with MVC and JavaScript for the migrations, but I’ve recently rebuilt some of our apps using Blazor WASM. Honestly, I find it a much more enjoyable and productive experience compared to working with MVC and JS.

[paulguk]

I look forward to the third instalment next year where Nick reviews Nick reviewing Nick.

[martinstanek]

We've migrated all our React apps to the Blazor and React devs, never looked back. It was one the the best decisions I've made as an architect. Our use-case might be niche, but works very well in our context.
Having said that, there is really nothing to disagree or to be mad about in Your first vid.
I've been in touch with Steven and guys from MS product team, we might follow-up on our use case and publish a success story.

[PticostaricaGS]

Blazor is amazing. We have worked with it for years, it speeds up development in more than 50%, faster ROI. No way we go back to Angular, React, nor Vue.

[gregorylouppe]

Blazor at work, and in production.
Ditched the Angular front-end along, which required waaay to complex setup to work as expected. 4 developers went from angry to happy.
Not to mention the need to upgrade the Angular version every 6 month is you want to keep up with the Google train.

[kudasol]

Blazor is amazing! I've already built several medium-scale apps with it. While I'm not entirely sure about using Blazor Server for large-scale applications, Blazor WebAssembly combined with a Web API works perfectly. For real-time scenarios, you can easily integrate SignalR. If you're good in JavaScript, you can combine it with Blazor to overcome any limitations.

[davidbrenchley]

Microsoft needs to eat it's own dog food. When anyone hears I use Blazor, the question is always - Is it ready for prime time? Is it enterprise ready? Microsoft needa to really push Blazor so companies know they can safely build enterprise apps with it and one way is if Microsoft uses themselves (a lot) and not just in some small projects here and there

[CodySkidmorenh]

Blazor addresses the challenge of enabling developers to build both the frontend and backend using the same language and toolchain. That's the problem it solves.

[meta]

Honestly I disagree. It's a much better development experience having backend and frontend in one project solution and one language. You can just create a project with your DTOs and use the same classes in backend and frontend. This means you don't have to re-create your types in the frontend or use other tools or technology to create the types from your API schema or something.
Also, this approach reduces dependencies and simplifies your tech stack. For many cases, Blazor gets the job done and there are great free UI frameworks like MudBlazor for example.
I'm currently using .NET backend + Vue frontend in some projects, and Blazor in others, and honestly I wish I would have used Blazor in all of them. It's just a better experience and the end product is not better or worse with Blazor in my opinion

[Tecerp]

In Spain there is a boom with Blazor, many developers do not want to return to other technologies, what was done in 10 hours with other technologies with 1 in Blazor is enough and with more organized and clean code and only c sarp

[julienbarach]

Using Blazor WASM in production for years. It's a pleasure to use it, feels a lot like Vue 2.
Now indeed I'm hoping Blazor will be successful and well adopted because as a Blazor developer I don't want to go back to this JS thing.

[TheOmokage]

I'm a team leader in Moscow. I used Blazor not so long ago, together with the framework from telerik. The project was something like a personal terminal for applicants who came to the service center. It works on all devices, documents are displayed on it, you can put an electronic signature, a physical signature, and it integrates with the main EDMS.

[MartinHAndersen]

Blazor is amazing 🤩
Have coded in many JavaScript frameworks. What a waste of time

[yogxoth]

What are you using instead of Blazor nowadays, Nick?

[Dustyy]

We use blazor in production at work, mid size company. The reason being that the ecosystem is pretty good, dev workflow super fast and easy to learn.

[veec]

Using blazor wasm at work and at home. Can say it's much faster for prototyping and debugging. We moved from an angular front end with .net back end, and it's made life much simpler. Biggest plus is the sharing of models between front end and back end and no longer introducing buds because of property name typos

[DotnetareaBr]

All these UI frameworks to just put a record in a relational database 🤷‍♂

[EldonElledge]

As a C# developer, I have not had a need to spend time learning React and Angular because of MVC and Razor pages and now Blazor. I love Blazor and what they are doing with it.
There is not anything React and Angular developers are doing that I cannot do with Blazor. I think it has a user base just like all other languages.

[krss]

I love Blazor and I'm working on a big project using it. It's the only technology I'm now looking at from Microsoft to the point that whole Aspire push was really annoying to me because I knew they were redirecting work force, partially from Blazor to some Aspire related thingies.
If they push Blazor more and show that WASM can be trusted and extremely useful, this will lead to some major changes on Web technology stack.