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 p

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.