> that all goes under a single unhelpful name (Copilot)
This isn't even a new dumb move for Microsoft. In the early 2000s, they applied the .NET brand to lots of random things that were completely unrelated to the runtime/framework: https://en.wikipedia.org/wiki/Microsoft_.NET_strategy
Yep. I've been an Xbox player since 2002. Huge Halo fan. Thousands of hours on 3 different generations of Xbox. I still have my Halo 3 special edition helmet. I keep up with gaming news and listen to multiple gaming podcasts every week.
But even I can't reliably name the last two generations of Xbox without a pause. I always have to stop for a second and think it thru because the naming scheme is so abysmal.
But that's my lived experience. I play Xbox games with friends who are playing on an Xbox console, but I'm playing on my Windows-based Legion Go or my Windows PC on a desk at home or even cloud rendered through a web browser on a Linux box.
Xbox isn't just a single physical hardware device. Its a platform for playing games.
I do agree though, the naming patterns for their consoles has been absolutely atrocious. I consider myself somewhat of a gamer but if you just gave me the list of consoles there's absolutely a non-zero chance I'd fail at picking the rankings of performance and age.
And ActiveX before that. It literally just meant self-activating COM objects but came to include a scripting host, OLE, CDO, and a multimedia framework.
Well, Visual Basic .net is based on the .net framework, can't deny that. It's a very different language from the previous non-.net Visual Basic versions, so much that some people rather argue that "Visual Basic" is the problematic part of the name, not the ".net".
Though also interesting to note that the development team at the time didn't feel like it was substantially a different language and the first VB.NET compiler was Version 7.
This isn't even a new dumb move for Microsoft. In the early 2000s, they applied the .NET brand to lots of random things that were completely unrelated to the runtime/framework: https://en.wikipedia.org/wiki/Microsoft_.NET_strategy