News for hackers. Stuff that matters.
Re:MapReduce, TensorFlow, Vertex: Google's bet to avoid repe... by acdha on Tuesday August 29, 2023 @08:41PM (#37316167)
AppEngine also hit the classic Google problem of missing attention to detail. I used it for a couple of projects in 2008/2009 and it just wasn’t competitive - cold starts were painful, you’d hit all of these gaps in features or random bugs in the tooling, etc. and while Datastore might scale it was consistently much slower than any mainstream SQL database so you really had to need that scaling.

That was the first project which trained me not to use Google products. I remember reporting by a ton of stuff and then never hearing back and things never improving until much (multiple years?) later when I’d stopped using it. I was profoundly unsurprised when AWS ate their lunch.

Re:MapReduce, TensorFlow, Vertex: Google's bet to avoid repe... by hn_throwaway_99 on Tuesday August 29, 2023 @09:12PM (#37316397)
> AppEngine also hit the classic Google problem of missing attention to detail.

Amen, amen, amen. This is so frustrating to me because in general I really like GCP as a platform, and I think they're doing great things with stuff like Cloud Run.

Case in point, I like Firebase a lot, and I think Firebase Auth (aka Google Identity Platform) is a great product. But it took them about 2.5 years between releasing their initial support for a second factor, which was originally SMS only, and allowing a TOTP (e.g. Google Authenticator/Auth) 2nd factor. And they still don't support "remember this device" functionality, so every time someone logs in they always need to enter the 2nd factor. I literally can't think of any major site (especially Google's own) that doesn't support "remember this device", and yet it just must be a detail that's not "important enough" to get someone at Google a promotion.

Re:MapReduce, TensorFlow, Vertex: Google's bet to avoid repe... by acdha on Tuesday August 29, 2023 @09:30PM (#37316546)
Yeah, the updates I’m still getting on parity-with-AWS tickets from before the pandemic just reminds me that nobody at Google gets promoted for removing warts.

They did close my textbook example of that but it took half a decade to implement HTTP to HTTPS redirects, which basically every large customer wants to make compliance easier:

https://issuetracker.google.com/issues/35904733

Re:MapReduce, TensorFlow, Vertex: Google's bet to avoid repe... by hn_throwaway_99 on Tuesday August 29, 2023 @10:06PM (#37316786)
Wow, that issue thread basically shows everything that's wrong with Google when it comes to dealing with business customers, though I do give them credit that it seems to have slightly improved near the end there: at least a Google PM was giving status updates and engaging with the commenters - before that for years it was just crickets.

Here is my similar (though not as long) example - point-in-time-recovery on postgres: https://issuetracker.google.com/issues/78448400. Interestingly, it had the same problem with 0 communication from a Google PM until early 2020, so maybe they hired someone at that time who convinced them you can't treat business customers the same way you do consumers.

Re:MapReduce, TensorFlow, Vertex: Google's bet to avoid repe... by jmugan on Wednesday August 30, 2023 @12:08AM (#37317550)
I had the same experience with AppEngine. I kept hitting snags and just couldn't get them solved so I gave up on it and moved to AWS.
Re:MapReduce, TensorFlow, Vertex: Google's bet to avoid repe... by carom on Wednesday August 30, 2023 @04:06AM (#37319007)
Exact opposite experience here. I love AppEngine and can't get Beanstalk to work for the life of me.