Thread by @davidfowl

Somethings that we tried to change when building ASP.NET Core:
- Removing all first chance exceptions (where possible).
- Remove scanning all assemblies on Startup to find things (controllers/hubs/plugins/etc). We try to do a bulk of the work during build...

So that startup time isn't impacted by the scan and load all types in all assemblies.
- Code over configuration. Configuration is read and configured by imperative code.
- DI everywhere, anywhere we call your code, you can inject dependencies

- No static APIs, the entire framework is testable and uses constructor injection. Places that use the service locator pattern only do so because they themselves are factories. The root of the universe is the is DI container.

This makes it trivial to create multiple isolated universes of the application host and run them in the same process.
- Logging *everywhere* by default the framework logs unhandled exceptions for you. If you plug a logging provider in, things will start showing up.

- We kept the OWIN style separation between servers and application code. Server implementations do are not aware of the middleware pipeline or hosting model.
- The HttpContext is a bag of features, things that get hoised to top level properties are deemed "more important".

It was also very important to keep the HttpContext server neutral to make sure we didn't get into exposing surface area again on servers that may not support it.