Microsoft can and will probably abandon Blazor just like Silverlight. People are already unhappy with Xamarin Forms being not supported as their focus shifted to rebrand the product and recreate everything under their own name. I would not choose Blazor over JavaScript as there is no benefit. Using C# for some data processing can be done via WASM without using Blazor.
There were many factors that led to the demise of Silverlight, it was not a case of MS abandoning it. With Blazor, being based on WASM - a standard that is widely across browsers and which has wide language base - it makes it more likely that it will stay with us for many years to come.
Of course, Blazor may move to the next version of the framework at some point in the future - just as is the case with Xamarin Forms moving to MAUI. These are examples of a technology evolving and I believe they are generally a good thing.
If your team's skills are focused on JavaScript, then I agree that there is probably little reason to adopt Blazor. However, the ability to build applications in the language that your team is most skilled in brings significant advantages. I am obviously talking there about the multi-language support of WASM, not Blazor specifically. But, for Blazor specifically, this brings all the advantages of the C# and Dotnet toolchain. Just from the developer perspective, the strong tool chain (IDE support, developer code-quality tooling, code scanning, and so on), does in my view bring strong advantages for larger applications and larger teams.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Microsoft can and will probably abandon Blazor just like Silverlight. People are already unhappy with Xamarin Forms being not supported as their focus shifted to rebrand the product and recreate everything under their own name. I would not choose Blazor over JavaScript as there is no benefit. Using C# for some data processing can be done via WASM without using Blazor.
There were many factors that led to the demise of Silverlight, it was not a case of MS abandoning it. With Blazor, being based on WASM - a standard that is widely across browsers and which has wide language base - it makes it more likely that it will stay with us for many years to come.
Of course, Blazor may move to the next version of the framework at some point in the future - just as is the case with Xamarin Forms moving to MAUI. These are examples of a technology evolving and I believe they are generally a good thing.
If your team's skills are focused on JavaScript, then I agree that there is probably little reason to adopt Blazor. However, the ability to build applications in the language that your team is most skilled in brings significant advantages. I am obviously talking there about the multi-language support of WASM, not Blazor specifically. But, for Blazor specifically, this brings all the advantages of the C# and Dotnet toolchain. Just from the developer perspective, the strong tool chain (IDE support, developer code-quality tooling, code scanning, and so on), does in my view bring strong advantages for larger applications and larger teams.