With .net 4 still in active use, the naming makes it harder
Microsoft has historically been pretty bad at naming stuff (sometimes hilariously so, see Microsoft PlaysForSure[1] for an example - spoiler: it surely didn't play for long).
The rebranding from .NET Core 3.1 to .NET 5, and from .NET 4.x to .NET Framework, did make sense to me though - and increasingly so as development continues on ".NET > 5" with yearly releases, while ".NET Framework 4.x" is in maintenance mode.
[0]:https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotn...
in my opinion, they should have kept "core" branding, but shortened it to ".NET" for marketing and only for marketing.
in a better world, Microsoft would ditch the name ".NET" altogether and invent a new one. like LVM (lightweight virtual machine)
While it was always called .NET Framework, it was very commonly referred to simply as .NET (e.g. .NET 4.5) - and the "Microsoft .NET" logo was widely used in .NET Framework branding/marketing.
- Colgate Kitchen Entrees
- Ayds Diet Candy
- Gerber in Africa (in many regions, it is customary for labels to show what's inside. Having a baby on the bottle is just weird)
- Chevrolet Nova (no va means "don't go")
- Clairol Mist Stick (in Germany. In German, Mist means manure)
- Pee Cola (Ghana)
- Puffs Tissues (Germany) (in German slang, Puff means brothel)
- Nokia Lumia (prostitute in Spanish slang)
- ISIS Chocolates (Belgium)
- Hitachi's Woopie Washing Machine (cute to a Japanese ear, but not to that of an English speaker)