Hacker News Reader

Comment by pjmlp | Hacker News Reader

What to expect, when Microsoft decides to do stupid things like renaming .NET Core into .NET 5, thus everyone that doesn't pay attention to Microsoft world keeps thinking .NET is Windows only, as the .NET Framework was always known as plain .NET in most circles.

View on HN

I can't tell you how many people are confused that (1) Microsoft dropped "Core" from .NET 5+, and that .NET 4.8 and .NET 8 are not the same thing.

Microsoft jumped from .NET Core 3 to .Net (Core) 5 to avoid people conflating .NET Core 4 with .NET Framework 4.

Now tech adjacent people in my world, including people from Microsoft, think .NET Core 8 and .NET Framrwork 4.8 refer to the same version.

Luckily that problem will go away as we do our now biannual ritual of upgrading .NET versions, frustratingly.

Easy, do you want links to podcast interviews from .NET team members where they mention this still being an issue with .NET adoption outside traditional Microsoft shops.

For example, see Mandy Mantiquila interview with Nick Chapsas, if I remember correctly it is one of them.

Microsoft Teams. Teams (Personal), Teams (Work and School), Teams (New). A year or so ago you night have had all three of these installed at the same time..

and that's AFTER they changed the names of Personal and Work. Before that, you'd have Microsoft Teams and Microsoft Teams. One was purple with a white T and the other was white with a purple T.

If you tried to login with the personal version, it would error-out but not give any indication you may be using the wrong version. Let's be real. NO ONE is using Teams in their personal life. /rant

They're just infuriating on every level when it comes to naming things.

Reply on news.ycombinator.com