Blazor makes me learn C# it has very nice features (webassembly, static typing of C# etc).
But only a few jobs for for this technology. I see mostly Angular + C#
Blazor is brand new.
The vast majority of jobs that you see advertised are not for working on brand new applications, they are for working on applications that are already several years old. It’s impossible for those applications to be using Blazor, because Blazor didn’t exist when the application architecture was designed.
As for newer applications, a proportion of them use Blazor. It’s still quite a low proportion because Blazor is new and relatively untested, and a lot of industries shy away from untested technologies, but it’s starting to gain ground for new projects.
So, multiply the fraction of jobs that are for new projects, by the number of new projects that use Blazor, and you end up with the very low number you’re looking at now. Give it 5 years, though, and there’ll be more and more jobs advertised that use Blazor.
If you’re looking for a job now, and want to work on Blazor, then finding a C# shop that has new projects in the pipeline might get you where you want – don’t expect to be working on Blazor straight away, but you may be able to get redeployed to a greenfield project after a while, and that’s where you’ll most likely find Blazor being used. You’ll also find that software houses that write software for their commercial customers are more likely to be doing greenfield projects, and more likely to be using the latest technologies, compare to in-house development teams that develop software internally.
Tech like this comes and go all the time, you can’t get hung up on it. If you want to avoid javascript there are lots of ways, like, don’t do web development! But learning one particular library and trying to find a job just because of it, is a dead end.
it is a somewhat new technology and many job descriptions will be older repeated ones.
we are starting a project shortly that is likely to use Blazor i can only imagine the market is going to grow
I started a new blazor server project in my Dev house for a complicated application, it’s doing quite well. I don’t need front end devs as such because my C# devs caught on quite quickly. I just need a UI designer now,
We are very happy with it.
Blazor has only been out since 2019, so It’s going to take some time. I haven’t even learned Blazor yet because I can get enough work with C#/Razor/WebApi/Bootstrap/SQL/JQuery. I actually haven’t even bothered to learn Angular or React because it’s just another framework. I’ll learn it when I need to learn it. It probably be a good idea for you to learn Angular if you are earlier in your career and you want a growth path.
You know after looking at that, I think I know why .NET developers don’t have a acronym like LAMP or MEAN… we don’t have a single vowel in our tech stack. Maybe if we cram IIS in there… and Azure… and drop the “J” because honestly we just edit what we found in someone else’s JQuery. So now we get: CIRWABS. A CIRWABS developer.
RECRUITER: “We need a “Sir-wabs” developer.”
ME: “It’s actually pronounced “See-Wabs. And I can even edit other people’s JQuery.”
RECRUITER: “Oh, great. So can you dunk?”
ME: “Like… is that a framework?”
RECRUITER: “No, like in basketball. Dunk. Like Lebron.”
ME: “How much is this paying?”
RECRUITER: “$25 an hour but it’s remote! We send you a laptop and basketball hoop.”
ME: “No, I can’t dunk like Lebron. But I can probably learn how to flop like Jokic.”
But also, if you go down the Blazor path, you could be first in line at companies that decide to do a project in Blazor and need people who can hit the ground running. There are definitely advantages in being one of the first people who know a technology in the job market.
A nicer acronym would be more marketable for .net guys
Blazor will fail just like Razor, IMO
The advent in popularity of JS/TS client side UI frameworks has caused backend frameworks to enter a trend of continually degrading usage and popularity, but that doesn’t mean Razor failed. It was a success that is becoming less relevant over time.