This week we've already had a new asp.net core which drops support for .net standard and only supports .net core.
And now, a new version of .net standard that .net fx isn't going to support.
We are right back at the mess of portable class libraries with all their different supported profiles.
It means app devs are constantly dealing with problems like "is this library I want to use, supported by all the targets my app needs to run on", and library devs have a mess of different frameworks and combinations to support, so inevitability drop a few of them unless they are a big project with lots of manpower.