Y
Hacker News
new
|
ask
|
show
|
jobs
by
SketchySeaBeast
820 days ago
I agree that's frustrating, but I doubt Microsoft will be able to ever outdo itself with its .NET Framework/.NET Core/.NET naming convention nonsense.
2 comments
giancarlostoro
820 days ago
.NET 7 and beyond consolidates Framework and Core. I think they're going to just stick to just .NET moving forward. Eventually Framework and Core will be EOL'd.
I do agree though, they did it very confusingly.
link
SketchySeaBeast
820 days ago
It's definitely better sorted now, but as a dev working in the .Net stack during the .Net 2.0 Core time, it was very confusing.
link
giancarlostoro
820 days ago
2.0? ;) I started with 1.0.1, which had very confusing versions like 1.0.1.1 and other weird nonsense... I wanted to scream at Microsoft.
link
RexM
820 days ago
Don’t forget .NET Standard.
Their naming for all of this is a disaster.
link
giancarlostoro
820 days ago
Standard was supposed to be the in-between for Framework and Core if I'm not mistaken, that will likely be phased out and EOL'd.
link
I do agree though, they did it very confusingly.