4 ms·
From what I can remember Datastore-> Firestore (and firestore is a PITA because you can only have one per project even though when interacting with apis you pa
by nojvek 6y ago
From what I can remember
Datastore-> Firestore (and firestore is a PITA because you can only have one per project even though when interacting with apis you pass in a database name. Go figure)
Remote build execution - deprecated. Our live systems went down because of it and they didn’t even send an email they were killing it. Some person just pressed the kill switch and even support was unaware.
Their gcloud stuff asks for upgrades all the time. Older gcloud sometimes breaks. Sometimes upgrading to newer gcloud breaks existing code that interfaces with it.
It’s not that bad, but yeah GCP doesn’t give a shit a bit backwards compat as the other players do.
You get the feeling, they don’t dogfood their own shit. Like their pricing calculator is unusable on iOS. It baffles me that their support says “there is a feedback button” but there is no feedback button. They seem to only care about chrome with their cloud.google.com interface.
It really makes me think “what were they thinking?”
- novaleaf 6y agofyi, I use cloud datastore, and there was a breaking change about 2 years ago going from beta to "release", but that's it. You don't need to upgrade your current datastore to firestore, at least I haven't got any "it will break" emails about it. However, I do generally agree about the rant. While datastore still works, I can't upgrade my node-js app because the newer node bindings for GCP break the api's, and I can't upgrade my app's Node version either because They decided to ship static WebRTC binaries for the node GCP packages and those arn't avaiable for node 12.x (for the old package version I'm using)