They really won't, though; Microsoft just does this kind of thing, over and over and over. Before everything was named "365", it was all "One", before that it was "Live"... 20 years ago, everything was called ".NET" whether it had anything to do with the Internet or not. Back in the '90s they went crazy for a while calling everything "Active".
If a large company has bought into "Co-Pilot", they want it all right? Or not, but let's not make carving anything out easy.
Just a thought.
So Microsoft isn't bringing copilot to all these applications? It's just bringing a copilot label to them? So glad I don't use this garbage at home.
So once we have signoff then my counterpart in Sharepoint/M365 land gets his "Copilot" for Office, while my reporting and analytics group gets "Copilot" for Power BI, while my coding team gets "Copilot" for llm assisted development in GitHub.
In the meantime everybody just plugs everything into ChatGPT and everybody pretends it isn't happening. It's not unlawful if they lawyers can't see it!
> In the meantime everybody just plugs everything into ChatGPT
I believe you meant "everyone plugs everything into ChatGPT for Co-Pilot"! A statement with its own useful ambiguities.
It is comical, but I can now make a serious addition to Sun Tzu's maxims.
“All warfare is based on deception.”
“To subdue the enemy without fighting is the acme of skill.”
"Approval is best co-opted with a polysemous brand envelope."
This often happens because the people inside are incentivized to build their own empire.
If someone comes and wants to get promoted/become an exec, there's a ceiling if they work under the an existing umberlla + dealing the politics of introducing a feature which requires dealing with an existing org.
So they build something new. And the next person does the same. And so you have 365, One, Live, .Net, etc
Then there's DirectX and its subs - though Direct3D had more room for expanded feature set compared to DXSound or DXInput so now they're up to D3D v12.
We're now on the back end of that, where Microsoft must again make products with independent substance, but are instead drowning in their own infrastructural muck.
System 360 OS/2 DB 2 MQ series. PC
It is like IBM just refused to entertain the idea of having competitors, why should it them name a database by any other name than DB?
Also, it is possibly the worst console name of all time.
I don't even know what Xbox is now, is it a service, is it a console, I'm not even joking really.
Also visual studio code Vs full fat visual studio. Thanks Microsoft you just made it more difficult to web search both products.
Full fat .Net Vs dotnet core Vs standard or is that .net.
"Oh you mean the original one?"
No the one that came after the 360.
"The third one?"
No that was the second one, the One was the third.
"OK what are they on now?"
The Series series.
"The Series series?"
Yeah the X and S. Don't confuse that with the Xbox One X or S, or the 360 S.
"Right but what's the difference?"
The X is better than the S because X is a bigger letter. But they run the same games, but they're different. They're the same though.
They probably should have called the WiiU the Super Wii or Wii 2 or something, but on the whole they've got a mostly coherent naming convention.
nes:snes = 6502
n64 = mips
gamecube:wii:wiiu = powerpc
switch:switch2 = armWe got the Steam Controller and the new... Steam Controller.
We also got the Steam machine, as well as the new Steam machine.
Lol
Wii is a game cube with a funny controller. Or, wii is a tv-only olde switch.
I appreciate that it has its own name due to being a transitional experience.