Why you shouldn’t build projects on Google Cloud (or, why are we still having these conversations?)

This story on Medium, about Google Cloud, is all too familiar to me (hat tip to Donkey). It mirrors my experiences with Google in 2009 and 2013.
   A company monitoring solar plants and wind turbines had Google pull their account twice. The Googlebot falsely claimed there was suspicious activity, with Google threatening to delete their account in three days. If their CFO, whose credit card was linked to the account, hadn’t replied in time, that would have been millions of dollars down the gurgler.
   The company’s warning: don’t build stuff on Google Cloud. Apparently AWS is safer.
   They were very lucky, because Google’s forums are littered with people whose accounts have also been unilaterally terminated, and they were never recovered. Some have lost income streams. Most went through the “proper channels”.
   My experience in helping a friend recover his blog nearly a decade ago showed just how unreliable these channels were, with a Google forum volunteer going out of his way to be obstructive, because you dared question the big G. Most volunteers actually seem offended you questioned Google, such is their adherence to the cult.
   Mind you, I’m still waiting, three years later, for an explanation about why our Amazon Associates’ account, nearly two decades old, was unilaterally deleted. Amazon claimed six months ago that the matter had been ‘escalated’. Still waiting. Google, too, gets back to you initially, but escalation results in nought.
   When things go wrong, US Big Tech doesn’t work, does it? We’ve actively avoided Google for nearly a decade, and began posting warnings about Facebook around that time, too.
   Thank goodness for companies like Zoho: in the 2010s, Indian tech works better, and people take greater responsibility.


You may also like




Leave a Reply

Your email address will not be published. Required fields are marked *