Make Blazor More Extensible about aspnetcore

[javiercn]

@codymullins thanks for contacting us.

In general, we do not make anything that we don't have a clear use case for public or virtual. Anything that we make public or virtual in that situation adds risk as it precludes us in the future from making changes.

We are open to making more things public / virtual and in general, adding additional extensibility points, when there are clear use cases and demand for them, but having an "extensible by default" policy adds a lot of risk to evolve the framework in the future without breaking existing users inadvertedly.

If you have concrete asks, please file separate issues with the concrete scenarios and asks for us to consider.

[codymullins]

as it precludes us in the future from making changes

Well, it doesn't. There are breaking changes all the time in .NET, I don't think Blazor should be treated any differently.

when there are clear use cases and demand for them ... adds a lot of risk to evolve the framework in the future

Innovation gets stifled this way. Having a more extensible, open model I believe would allow more innovation from the community, not just what gets approved by the .NET team.

JavaScript doesn't have "internal" or "sealed" things and UI frameworks built for the JS community has more innovation outside of the maintainer - you can replace things, upgrade them, enhance them.

Please, for the sake of the future of Blazor and growing usage, consider having things less locked down.

[codymullins]

Seems like there is support for more innovation in the Blazor space at the risk of breaking changes: https://x.com/codemullins/status/1793691901771575784

@danroth27 - can we discuss this a bit more?

[gragra33]

@codymullins There is a new feature coming to C# 13 that will address this for you. Watch this video from @Elfocrash The New Extensions EVERYTHING Feature of C# 13!