Poorly written article. But overall I can understand the enthusiasm the author is expressing for .Net Core.
I am programming with it since 1.0 and we already have a big productive application running on it. Every update brings needed features like EF Core improvements in 2.1. and also it gets easier to upgrade.
3.0 will be very interesting since microsoft is indicating a shift to .Net Core away from .Net Classic.
Combined with Visual Studio Code I can see C# and .Net core as a very good alternative to be taught at schools and universities since its easier to pick up with the right guidance.
We are replacing out homegrown PHP ERP system with ASP.NET Core MVC since Version 1.0.
It is a blast to work with LINQ and Lambdas and I really miss it in other languages. EF Core also matures quickly and we sucesssfully connected it to mysql and sql server.
So far there hasn't been a problem we couldn't solve in .Net Core.
For a small side project I used .Net Core Razor Pages very productively. Only needed the SDK and visual studio code. Planning on moving more small stuff away from python to .net core based on that.
Really looking forward to Version 3.0 and Kestrel replacing IIS for good.
On the other hand, as soon as banks become really big, they loose interest in ordinary customers.
In Switzerland the services of big banks like Credit Suisse or UBS are getting worse while getting more expensive at the same time.
This causes people to switch to smaller local banks because they can better tend to their needs and are more willed to grant them loans.
That's exactly why the rule of 72 should be thought more often. Just seeing how quickly the population can double at the current growth rate is an eye opener.
I just installed it and my .Net Core 2.0 Application worked instantly, so far I am very pleased with the performance.
One big plus I see in Rider is the same Git Integration they use in PHPStorm. In Vistual Studio Git was always a bit of a second class citizen because of TFS