Re:How Figma's databases team lived to tell the scale
by victor106 on Thursday March 14, 2024 @04:03PM
(#39708349)
> yet another one of Microsoft’s typical product naming crapshoots.
Well said. I haven't seen any company as terrible as Microsoft at naming things. Anyone know why?
Re:How Figma's databases team lived to tell the scale
by studmuffin650 on Thursday March 14, 2024 @05:04PM
(#39708956)
AWS is putting up good fight
Re:How Figma's databases team lived to tell the scale
by salynchnew on Thursday March 14, 2024 @05:18PM
(#39709093)
Naming things is hard.
At a previous employer, I saw several cool-ish open source projects instantly doomed to obscurity by picking a name that either completely duplicated the name of an existing OSS project or were guaranteed to have terrible SEO for another reason.
However, Microsoft seems to have a unique crossover of fragmented business units and centralized marketing. That's why you end up with Azure -> Subproject -> Actual Product/Service word soup. Perviously, they did this with the Windows Live brand from 2005-2012, and "Xbox" for a wide range of gaming projects (many of which were on PC).
Re:How Figma's databases team lived to tell the scale
by thomasjudge on Thursday March 14, 2024 @06:55PM
(#39709947)
related, Microsoft on Microsoft marketing:
Maybe because CitusData was bought by Microsoft around the same time, so Microsoft could create “Azure Cosmos DB for Postgres Cluster”, yet another one of Microsoft’s typical product naming crapshoots.