3 ms·

So much ranting, yet not a single example of a GCP product that Google has actually killed. Got examples? I mean, there's stuff like Python 2 support being su

So much ranting, yet not a single example of a GCP product that Google has actually killed. Got examples? I mean, there's stuff like Python 2 support being sunset on managed services, but as Yegge himself points out that's on Guido, not GCP.

gostsamo 6y ago
No, the difference between python2 and python3 in the managed services goes much beyond unicode in the Google universe. The most obvious example is that in app engine standard python 2 you can send and receive emails while you need a third party service in python 3. In my other comment I've mentioned some other issues when Google start neglecting stuff.
- cpcallen 6y ago
  Yes; exactly this. I'm contracted to Google, and so much of my Googler colleagues' time has been wasted in the last year porting projects off of the Python 2 APIs which are about to be shut down. Are they porting to the AppEngine Python 3 APIs? Hell no: those are totally useless (no BigTable, no user authentication, etc.). If you have to rewrite everything to replace all the functionality that used to be "batteries included", you might as well build something can run on any old bare VM instead, and so—like any sensible external developer—my colleagues are doing everything they can to avoid depending on any Google-specific APIs, libraries or platforms. I really though AppEngine and PaaS were the future, but evidently that future will not be written at Google.
  - erichocean 6y ago
    > Are they porting to the AppEngine Python 3 APIs? Hell no: those are totally useless (no BigTable, no user authentication, etc.). That's hilarious(ly bad): BigTable was like the main selling point of OG AppEngine, and they practically forced their user authentication scheme on you too.
    - 9nGQluzmnq3M 6y ago
      I think you mean Datastore, not Bigtable?
joepie91_ 6y ago
The old Firebase API. No longer possible to create new databases that can be used from the old API. Which in practice meant that "migrating to a new database under a different account" translated into "rewriting half a codebase due to a cascade of breaking changes in the surrounding tooling".
- deleted 6y ago
  [deleted]
- zwily 6y ago
  Are you talking about the Firebase RTDB? You can’t create new ones anymore? That’s news to me.
nacs 6y ago
He gave a few in the article.. > > I know I haven’t gone into a lot of specific details about GCP’s deprecations. I can tell you that virtually everything I’ve used, from networking (legacy to VPC) to storage (Cloud SQL v1 to v2) to Firebase (now Firestore with a totally different API) to App Engine (don’t even get me started) to Cloud Endpoints to… I dunno, everything, has forced me to rewrite it all after at most 2–3 years, and they never automate it for you, and often there is no documented migration path at all. It’s just crickets.

gostsamo 6y ago

No, the difference between python2 and python3 in the managed services goes much beyond unicode in the Google universe. The most obvious example is that in app engine standard python 2 you can send and receive emails while you need a third party service in python 3. In my other comment I've mentioned some other issues when Google start neglecting stuff.

cpcallen 6y ago
Yes; exactly this. I'm contracted to Google, and so much of my Googler colleagues' time has been wasted in the last year porting projects off of the Python 2 APIs which are about to be shut down. Are they porting to the AppEngine Python 3 APIs? Hell no: those are totally useless (no BigTable, no user authentication, etc.). If you have to rewrite everything to replace all the functionality that used to be "batteries included", you might as well build something can run on any old bare VM instead, and so—like any sensible external developer—my colleagues are doing everything they can to avoid depending on any Google-specific APIs, libraries or platforms. I really though AppEngine and PaaS were the future, but evidently that future will not be written at Google.
- erichocean 6y ago
  > Are they porting to the AppEngine Python 3 APIs? Hell no: those are totally useless (no BigTable, no user authentication, etc.). That's hilarious(ly bad): BigTable was like the main selling point of OG AppEngine, and they practically forced their user authentication scheme on you too.
  - 9nGQluzmnq3M 6y ago
    I think you mean Datastore, not Bigtable?

joepie91_ 6y ago

The old Firebase API. No longer possible to create new databases that can be used from the old API. Which in practice meant that "migrating to a new database under a different account" translated into "rewriting half a codebase due to a cascade of breaking changes in the surrounding tooling".

deleted 6y ago
[deleted]
zwily 6y ago
Are you talking about the Firebase RTDB? You can’t create new ones anymore? That’s news to me.

nacs 6y ago

He gave a few in the article.. > > I know I haven’t gone into a lot of specific details about GCP’s deprecations. I can tell you that virtually everything I’ve used, from networking (legacy to VPC) to storage (Cloud SQL v1 to v2) to Firebase (now Firestore with a totally different API) to App Engine (don’t even get me started) to Cloud Endpoints to… I dunno, everything, has forced me to rewrite it all after at most 2–3 years, and they never automate it for you, and often there is no documented migration path at all. It’s just crickets.