Several hosting providers have added ASP.NET Core 1.0 to their offer. In other words after near four years of client-side presence .NET Core is now on duty at server-side.
The hardware and communication technologies emerging after the first version of the .NET Framework have made necessary a major redesign of Microsoft's managed code environment, and finally .NET Core is ready to go for early adopters.
Some people testing or evaluating ASP.NET Core's feature set are wondering why it doesn't include a mailer, an image processing library, a DataAdapter or SignalR implementation?
In my opinion this happens because it has been designed as a modern multi-platform tool with loosely coupled architecture and dockers in mind, employing with maximum efficiency the appropriate platform-specific software resources.
The server-side operating system of your choice already has native tools for mailing, charting, generating images, rich text, data sheets or handling multimedia files, and those tools will certainly work with better speed and stability than a generic library.
ASP.NET as a middleware does not need to double the role of a web server, a game server or a media streamer, those roles are normally delegated to specialized local processes - their concrete pros and cons depending on the server operating system or your third-party vendors.
From project management point of view defining clearly the objectives and domain of relevance are key aspects of a successful project, thus in my opinion ASP.NET Core is on the right track and it's a good choice for new projects with service-oriented architecture.