3 ms·
Indeed, way too confusing. ".NET Core 5 is now .NET Core 1.0. " Really? What happens when .NET Core v 2.0 comes out? .NET is drowning in a confusion of its ow
by RachelF 11y ago
Indeed, way too confusing.
".NET Core 5 is now .NET Core 1.0. " Really? What happens when .NET Core v 2.0 comes out?
.NET is drowning in a confusion of its own making.
- taspeotis 11y ago> ".NET Core 5 is now .NET Core 1.0. " Really? What happens when .NET Core v 2.0 comes out? Is your point that v2 ... v3 ... v4 will eventually overlap with .NET Core 5? Because .NET Core 5 hasn't actually been released yet.
- cm2187 11y agoI think it's worse. When you will be googling a question for .Net core 2.0, you will find responses for .Net 2.0. But .Net core is not backward compatible, they removed lots of stuff. We would have been better off if they had called it "Monkey 1.0" instead of ".Net Core 1.0".
- khellang 11y agoEven if it had shipped, what's stopping them from skipping 5 and "turn it up to 6"? ;)