> Looks like MS realized they made a mess with .net core
Looks like .NET Core did exactly what it was supposed to; provide a early-usable bridge to where .NET was headed for the people who didn't have legacy compatibility requirements while the implementation hat was the future got to the point where it could subsume the role of the legacy .NET Framework.
> Now they are abandoning again this new '.Core' bandwagon...
No, they are abandoning the old .NET Framework, because everything needed will now be implemented in .NET Core. They are also then skipping a major version in the numbering for .NET Core (so that the version number is also greater than the last-ever .NET Framework version) and dropping the modifier “Core” from the branding because there is no longer a “.NET Framework” for core to be contrasted against.
actually i think .net 5 will clear a lot of stuff up. basically there is no more naming confusion and once we are on asp.net 6 no version conflicts will ever be there.
its the best step they could do.
they also communicate clearly now that there will only be one dotnet implementation in the future, .net 5 and forward. in the past there was no clear message what will happen with mono, .net4x, etc...
Sure, but you can view things as "where do I assign blame" or "what are my fixed inputs." If you look for something to blame, maybe it's that people lack reading comprehension. If it's enough people getting confused, and it matters to you that people understand things -- even if things would be solved by them reading/understanding the right things, you need to change what you can change, because you can't change your fixed inputs (in this case, your audience).
Looks like .NET Core did exactly what it was supposed to; provide a early-usable bridge to where .NET was headed for the people who didn't have legacy compatibility requirements while the implementation hat was the future got to the point where it could subsume the role of the legacy .NET Framework.
> Now they are abandoning again this new '.Core' bandwagon...
No, they are abandoning the old .NET Framework, because everything needed will now be implemented in .NET Core. They are also then skipping a major version in the numbering for .NET Core (so that the version number is also greater than the last-ever .NET Framework version) and dropping the modifier “Core” from the branding because there is no longer a “.NET Framework” for core to be contrasted against.