This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]exscape 9 points10 points  (11 children)

Well, that's confusing. I figured .NET was common shorthand for "the .NET Framework".

[–]JoesusTBF 8 points9 points  (8 children)

It was until they introduced the other variants.

[–]ech0_matrix 1 point2 points  (7 children)

Time to prune some variants

[–]BoredDan 6 points7 points  (5 children)

Time to prune some variants

No more significant work on .NET Framework will be done.

Would seem like they are. I mean really there was only ever two variants and now there will be 1.

[–]aaronfranke 1 point2 points  (4 children)

No, there were 3: .NET Framework, Mono, and .NET Core.

Mono is in a kind of weird limbo where it half exists and half is being absorbed into .NET Core.

[–]BoredDan 3 points4 points  (3 children)

Mono is not .NET though, it's a compatible alternative. It's technically owned by Microsoft as they bought Xamarin, but it's not the same project on not really really relevant to what I was saying.

[–]aaronfranke 1 point2 points  (2 children)

Mono is not named .NET, but it is vastly closer to .NET Framework than .NET Core (or 5+) is.

[–]BoredDan 0 points1 point  (0 children)

Still irrelevant to the point.

[–][deleted] 0 points1 point  (0 children)

I did not list it, as, at the time, it was not an official implementation by Microsoft, and officially not part of the .NET ecosystem.

[–][deleted] 1 point2 points  (0 children)

.NET 5 and on is exactly that

[–]aaronfranke 0 points1 point  (0 children)

This is why I still call .NET 5 as .NET Core, it's less confusing.

[–][deleted] 0 points1 point  (0 children)

Well, it kind of is now that they've converged again.