That's not even the best example. .NET Core vs. .NET Standard was a wtf?
At least they named it core and standard so you know which mess you're referring to.
With Apple TV you have to make up your own qualifiers.
Apple's marketing team seems to failing at their jobs right now. They had iPhone had X/Xr/Xs/Xs Max at some point, and I never figure out which was which. The most recent 11/11 pro/11 pro max makes a lot more sense, but it sounds dated.
.Net Core and Standard are two of the best things Microsoft has done in the past 5 years and part of the reason why .Net is doing so well and is super popular.
.NET Core is the best thing Microsoft did even if it sucks they basically redid .NET Framework. It sucks when companies do that kind of thing but the end result is a much more powerful .NET ecosystem. The confusing bit is old .NET Framework libraries that may or may not work at all with .NET Core.
Microsoft has the .Net ecosystem (as the above poster described it "Microsoft's Java," which it largely is). However for a period Microsoft was naming other products and services ".Net" that were completely unrelated. Specifically this: https://en.wikipedia.org/wiki/Microsoft_.NET_strategy
Both .Net Core and .Net Standard are part of the .Net ecosystem for real, making them not an example of the marketing phenomenon being discussed here. Which isn't to say the names aren't confusing, just that it isn't in the same pattern.
PS - .Net Framework: Legacy/Classic .Net. Windows Only. Started in 2002. 4.8 is the final major version.
.Net Core: Light weight/cross platform "reboot" of .Net Framework. Started in 2016.
.Net Standard: Minimum subset of both that allows libraries to be cross-compatible with .Net Framework and .Net Core. Also assures they lack Windows specific dependencies. Allowing a bridge to migrate to .Net Core.