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.
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.
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 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."