Google has terrible support. I used AWS and Google clouds in parallel for a while and the difference was day and night. GCE support issues take anywhere from 2

Google has terrible support. I used AWS and Google clouds in parallel for a while and the difference was day and night. GCE support issues take anywhere from 2 days to 3 days for the first response (depending on timezone differences), while with AWS someone usually contacts within hours, if I just crib on the twitter account. There are only positive surprises with AWS, while negative surprises only with GCE (like their recent maps pricing debacle, retiring Datastore APIs, etc). AppEngine was ahead of the competitors a few years back. But it was/is neither as easy as heroku, nor as kept updated as the competitive PaaS solutions. We have beanstalk, lightsail etc. in AWS. Appengine flexenv takes about 10 minutes whenever we change the container sources, and the GCE team believes that it is acceptable :( Golang was invented at Google but AWS Lambda added support for serverless golang a looooooong time ago, while CloudFunctions from Google is still in a private closed beta which probably none outside Google use. Also, I have been burnt by Google obsoleting their Datastore APIs and expecting the whole world to move as fast as them, while my apps written for dynamodb continue to run without requiring changes for years. Also, firebase, stackdriver (opentracing vs observability) etc. seem to go on various directions, with different documentation formats, tutorial styles, dashboard styles, etc. in contrast to AWS services, which offer a more cohesive, uniform experience. Some of us at $DAYJOB are big fans of google technologies but always end up choosing AWS due to the much superior support of the latter. It often feels to me like Google is in the public cloud business only as an afterthought and not even fully interested in it.