3 ms·

If you are a junior developer please do not go anywhere near this, your career will be stunted.

jiggawatts 3y ago
That’s terrible advice. You’re assuming all the world is identical to Silicon Valley and its startup culture of bashing things with open source rocks instead of just buying a proprietary power tool. Outside of that pond, there is a giant ocean of developers that work in enterprise and make a perfectly respectable income.
- unsignedint 3y ago
  Indeed, within an enterprise environment featuring a pre-established C# backend, I've discovered that Blazor, particularly Blazor Server, offers exceptional productivity. It essentially facilitates the deployment of a web front end with minimal overhead.
- phillipcarter 3y ago
  I wouldn't say it's necessarily bad advice. Even in the enterprise where .NET has the most adoption, most people building web apps are doing so with JS/TS. I really doubt Blazor will get big enough so as to be the primary way people build web UIs. Doesn't mean it's not worth learning, but I would agree that a junior shouldn't focus on Blazor first.
  - samayylmao 3y ago
    I think it's bad advice because the fundamentals of web development and core programming concepts are mostly transitive between frameworks. You can learn that on blazor and apply it elsewhere. That being said I have worked with blazor since launch in 2019 and it's one of my least favorite SPA frameworks.
    - jiggawatts 3y ago
      I’m curious to hear any specific critique you have of Blazor.
      - samayylmao 3y ago
        My specific critiques revolve around the state of tooling and the developer experience. I went into [some detail](https://news.ycombinator.com/item?id=37798121 https://news.ycombinator.com/item?id=37798121) on another comment on this thread.
johnfn 3y ago
This is nonsense. If you're a junior developer, don't listen to advice from people who claim that your career will be "stunted" by learning non-traditional frameworks.
jjtheblunt 3y ago
That looks myopic, suggesting the dotnet ecosystem is somehow deficient when it’s super reliable and widely used, but perhaps less vocally.
- Someone1234 3y ago
  They were talking about Blazor. You're talking about dotnet as a whole. I agree with them on Blazor and I agree with you on dotnet (e.g. WebAPI) too. The two positions aren't mutually exclusive. Being a Blazor developer will definitely be career limiting. I'd take almost any other skill set on a new hire (e.g. Angular, React, .Net MVC, Java, et al). The only thing it may beat is Web Forms/Visual Basic, because at least you'll know modern C# syntax. But I'm not allowing Blazor in any codebase I control.
  - achandlerwhite 3y ago
    Learning Blazor and “being a Blazor developer” are two different things.
tonyedgecombe 3y ago
I think you are probably right. It's very easy to get stuck in a career dead end in technology and digging yourself out can be difficult.
migf 3y ago
I agree. I think frameworks that hide the client server interplay are bad. This type of technology teaches magical thinking that doesn't live up to its promises as soon as you go a little off the beaten path and is more frustration than it's worth. Having said that, first job is a first job. Take that c# you learn to a REST backend job once you have a couple years experience.

That’s terrible advice. You’re assuming all the world is identical to Silicon Valley and its startup culture of bashing things with open source rocks instead of just buying a proprietary power tool. Outside of that pond, there is a giant ocean of developers that work in enterprise and make a perfectly respectable income.

unsignedint 3y ago
Indeed, within an enterprise environment featuring a pre-established C# backend, I've discovered that Blazor, particularly Blazor Server, offers exceptional productivity. It essentially facilitates the deployment of a web front end with minimal overhead.
phillipcarter 3y ago
I wouldn't say it's necessarily bad advice. Even in the enterprise where .NET has the most adoption, most people building web apps are doing so with JS/TS. I really doubt Blazor will get big enough so as to be the primary way people build web UIs. Doesn't mean it's not worth learning, but I would agree that a junior shouldn't focus on Blazor first.
- samayylmao 3y ago
  I think it's bad advice because the fundamentals of web development and core programming concepts are mostly transitive between frameworks. You can learn that on blazor and apply it elsewhere. That being said I have worked with blazor since launch in 2019 and it's one of my least favorite SPA frameworks.
  - jiggawatts 3y ago
    I’m curious to hear any specific critique you have of Blazor.
    - samayylmao 3y ago
      My specific critiques revolve around the state of tooling and the developer experience. I went into [some detail](https://news.ycombinator.com/item?id=37798121 https://news.ycombinator.com/item?id=37798121) on another comment on this thread.

johnfn 3y ago

This is nonsense. If you're a junior developer, don't listen to advice from people who claim that your career will be "stunted" by learning non-traditional frameworks.

jjtheblunt 3y ago

That looks myopic, suggesting the dotnet ecosystem is somehow deficient when it’s super reliable and widely used, but perhaps less vocally.

Someone1234 3y ago
They were talking about Blazor. You're talking about dotnet as a whole. I agree with them on Blazor and I agree with you on dotnet (e.g. WebAPI) too. The two positions aren't mutually exclusive. Being a Blazor developer will definitely be career limiting. I'd take almost any other skill set on a new hire (e.g. Angular, React, .Net MVC, Java, et al). The only thing it may beat is Web Forms/Visual Basic, because at least you'll know modern C# syntax. But I'm not allowing Blazor in any codebase I control.
- achandlerwhite 3y ago
  Learning Blazor and “being a Blazor developer” are two different things.

tonyedgecombe 3y ago

I think you are probably right. It's very easy to get stuck in a career dead end in technology and digging yourself out can be difficult.

migf 3y ago

I agree. I think frameworks that hide the client server interplay are bad. This type of technology teaches magical thinking that doesn't live up to its promises as soon as you go a little off the beaten path and is more frustration than it's worth. Having said that, first job is a first job. Take that c# you learn to a REST backend job once you have a couple years experience.