The ASP.NET Core configuration relies on a Startup class that should have one Configure method and that can optionally include a ConfigureServices method.
I was wondering why not force this class to implement an interface containing those two methods to get all the benefits of strong typing.
I know that the true reason lies unreachable in the mind of the designers of the framework, but can anybody give a good reason about why they might have chosen not to use an interface?