5 ms·
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
by 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 agoIndeed, 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 agoI 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 agoI 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 agoI’m curious to hear any specific critique you have of Blazor.
- samayylmao 3y agoMy 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.