Is the .NET Core pie fully baked yet?

Overview of .NET Core vs .NET Framework
I must admit, I have not thought too highly of the whole .NET core effort that has been going on the last 2 years or so.  When Microsoft changes its technology stack, its often a big bucket of Legos dumped on you all at once.  However, this time it was even more confusing because there was more than one bucket! That said, I have had the view that this was the direction things were headed for a while, regardless of Microsoft's claim that they will continue to develop both the framework and .net core stacks. Its hard to imagine them eventually not developing things to the point they are one set of API's, which isn't the case now. That might mean yet another name change...

Where are we now?
As it stands, you can still develop a new application with MVC5 or use MVC6 (ASP.NET core) with the full framework, or use the .NET core libraries.  Confused yet?  Then there is .NET Standard.  Uh oh. I'm not the only one. However, things seem to be settling down now, and at least for new applications, ASP.NET Core might just make sense.  If for no other reason, than the new project structure which makes using something like Angular and associated NPM libraries much easier.
 
Where is this headed?
Good question.  Even though Microsoft claims they will continue to develop the full framework AND .net core, its likely that the focus will be on the .net core stack.  Just a guess.

When to choose one over the other. link