Forum Discussion
How is going Blazor?
Hey guys, I'd like to know how is the market for web development with blazor. Ppl really adopted this and why use blazor instead others frameworks like React, Angular or Vue? Thanks in advance!
I'll try to avoid bias because I'm a massive .NET fanboy. I'm currently pushing all of my companies business application development to Blazor for a few reasons:
It removes the need (for the most part) for using JavaScript/TypeScript which makes the hiring process easier as I can take pure .NET (desktop or web) developers and get them learning Blazor framework without the need for getting to grips with unfamiliar syntax or nuances of a different language.
The learning curve is tiny in my opinion, if you've already been coding in C#. As an anecdotal example, I took on a junior developer 8 months ago as his first development role and he is producing some very professional frontend work using just Blazor and the out-the-box bootstrap with very little intervention from myself or the seniors on my teams.
I tentatively kept an eye on Blazor when the first preview was released as you never know how it's going to play out but Microsoft have absolutely convinced me of the potential and provided some brilliant road maps for the future. I'm particularly interested in the way various web techs are now slotting together. First there's the MAUI/Blazor hybrid bringing web and mobile closer and then news of Blazor United to unify server side and WASM Blazor hopefully coming fr .NET8.
As far as the market goes on the wider scheme, I know there are few Blazor developers about in comparison to React, Angular, etc, as it is an emerging technology. I usually hire through recruiters as they have a large pool of developers to contact and they confirm the lack of developers with significant production experience but I do see that changing as I know a few other development managers who have started eyeballing Blazor for their new web applications.
If anyone was to ask for the purpose of learning to go for a Blazor specific position, I'd say give it a go and spin up a couple personal projects. Anyone with C# experience can make a couple components and get some data passing with EventCallbacks/Cascading parameters and they'll be well on their way.
Have yourself a wonderful day,
Gav
2 Replies
- Gavin-WilliamsCopper Contributor
I'll try to avoid bias because I'm a massive .NET fanboy. I'm currently pushing all of my companies business application development to Blazor for a few reasons:
It removes the need (for the most part) for using JavaScript/TypeScript which makes the hiring process easier as I can take pure .NET (desktop or web) developers and get them learning Blazor framework without the need for getting to grips with unfamiliar syntax or nuances of a different language.
The learning curve is tiny in my opinion, if you've already been coding in C#. As an anecdotal example, I took on a junior developer 8 months ago as his first development role and he is producing some very professional frontend work using just Blazor and the out-the-box bootstrap with very little intervention from myself or the seniors on my teams.
I tentatively kept an eye on Blazor when the first preview was released as you never know how it's going to play out but Microsoft have absolutely convinced me of the potential and provided some brilliant road maps for the future. I'm particularly interested in the way various web techs are now slotting together. First there's the MAUI/Blazor hybrid bringing web and mobile closer and then news of Blazor United to unify server side and WASM Blazor hopefully coming fr .NET8.
As far as the market goes on the wider scheme, I know there are few Blazor developers about in comparison to React, Angular, etc, as it is an emerging technology. I usually hire through recruiters as they have a large pool of developers to contact and they confirm the lack of developers with significant production experience but I do see that changing as I know a few other development managers who have started eyeballing Blazor for their new web applications.
If anyone was to ask for the purpose of learning to go for a Blazor specific position, I'd say give it a go and spin up a couple personal projects. Anyone with C# experience can make a couple components and get some data passing with EventCallbacks/Cascading parameters and they'll be well on their way.
Have yourself a wonderful day,
Gav
- phcmiguezCopper Contributor
Firstly thank you so much for your answer! It covered all my doubts about Blazor!
I'll invest in learning this technology!
Have a great day!!!