Live data from Hacker News

Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

theinformation.com

721–730 of 856 posts

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#721
post #690

Earlier quoted context omitted.

The issue for me isn't Reader itself but what it says about the disconnect between Google management and us, the users of Google products. That seems to have happened around the time Google went from _having_ a "user base" to being effectively ubiquitous. I can't speak for others, but Google of the 2000s "got" the hacker/nerd mindset in a way that was the closest thing to empathy I've ever felt from a corporation. Th…

Free consumer products are not the same as paid enterprise services. The markets are entirely different, and ascribing the fate of Google Reader as a sign of anything on the B2B front doesn't make sense.

Feelings often don't make sense, but you can't 'logic' feelings away that easily. Or I can't, anyway.

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#722

Googler here. My opinions are my own; I have no non-public knowledge on this topic. I do not understand the hyperbole around this report. Nowhere does it say that Google plans to shutter GCP if it doesn't reach #1 by 2023. > said people with knowledge of the matter. As in, people who may not have even been at said meeting which took place nearly two years ago, under a different VP and now a different CEO, and saw som…

> So it's not about being #1, it's about being profitable. The problem Google has with the developer community is largely around the fact that Google has a long history of pulling the rug out from our feet. There have been 3 stories on HN in the past couple weeks alone about Google products which have either been dropped or changed significantly such that they are no longer viable for developers to use. Google has lo…

Eh, I have to point out that AWS has many services that receive such scant updates that they are effectively dropped products.

There are a lot of things that AWS produces which never receive adequate polish or timely updates. I’ve been in betas for more than a few new offerings and was stunned at how incomplete and buggy these offerings were. More than a year later, they remain in a half usable state.

Google dumps things it’s not committed to making great. AWS maintains numerous things which are half usable, poorly documented, and incomplete. It all depends on the context, but in some ways I prefer drops to half-assed products.

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#723

Googler here. My opinions are my own; I have no non-public knowledge on this topic. I do not understand the hyperbole around this report. Nowhere does it say that Google plans to shutter GCP if it doesn't reach #1 by 2023. > said people with knowledge of the matter. As in, people who may not have even been at said meeting which took place nearly two years ago, under a different VP and now a different CEO, and saw som…

Instead of spending time posting stuffs here, could your Googlers get back to your work to improve GCP's quality? Poor availability, of no help customer support, and slow fix of any problems is killing GCP.

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#724
post #540
post #435

Earlier quoted context omitted.

If you think the API mandate necessitated or created AWS then yes, you misunderstand that memo. The API memo simply mandated a service-oriented architecture. That can run on any compute and indeed predates AWS by several years. The origins of AWS are entirely unrelated, Amazon simply realized it was good at operating infrastructure. This led to the conception of offering infrastructure as a service. The initial AWS s…

I'm confused because on the one hand you say that their needs are very different and then on the other hand you say that they are using AWS. Another commenter also pointed out that they are using AWS. I think the only needs that are likely different are scale, so bigger instances, and the fact that they have a massive legacy infrastructure that can't be easily migrated off of. So that's pretty much what I would expec…

Amazon uses AWS for some new stuff. New AWS services high up in the stack like AI services run mostly on AWS. Most infra-AWS services run on foundational AWS services like EC2 and S3. Foundational AWS services (EC2, S3, DynamoDB, etc.) don't run on AWS for obvious chicken-and-egg reasons. For all of the things that are done by latecomer AWS services you can count on there being an unrelated internal tool, since clearly Amazon was doing those things before they launched those services.

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#725
post #690

Earlier quoted context omitted.

The issue for me isn't Reader itself but what it says about the disconnect between Google management and us, the users of Google products. That seems to have happened around the time Google went from _having_ a "user base" to being effectively ubiquitous. I can't speak for others, but Google of the 2000s "got" the hacker/nerd mindset in a way that was the closest thing to empathy I've ever felt from a corporation. Th…

Free consumer products are not the same as paid enterprise services. The markets are entirely different, and ascribing the fate of Google Reader as a sign of anything on the B2B front doesn't make sense.

> Free consumer products are not the same as paid enterprise services.

They may have different revenue models, but there is little difference when it comes down to management killing services which aren't profitable.

If there is a difference, it is that Reader could be maintained at little cost, while GCE (when it gets the axe) could potentially be costing google hundreds of millions per year to keep running.

There have been plenty of other cases where google has burned bridges with the technical crowd which they should have embraced as champions for selling services. Killing off XMPP support was another prime one for me, and absolutely affected paid enterprise customers as well.

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#726
post #690

Earlier quoted context omitted.

The issue for me isn't Reader itself but what it says about the disconnect between Google management and us, the users of Google products. That seems to have happened around the time Google went from _having_ a "user base" to being effectively ubiquitous. I can't speak for others, but Google of the 2000s "got" the hacker/nerd mindset in a way that was the closest thing to empathy I've ever felt from a corporation. Th…

Free consumer products are not the same as paid enterprise services. The markets are entirely different, and ascribing the fate of Google Reader as a sign of anything on the B2B front doesn't make sense.

This is not an economic problem. It is a trust problem.

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#727

Googler here. My opinions are my own; I have no non-public knowledge on this topic. I do not understand the hyperbole around this report. Nowhere does it say that Google plans to shutter GCP if it doesn't reach #1 by 2023. > said people with knowledge of the matter. As in, people who may not have even been at said meeting which took place nearly two years ago, under a different VP and now a different CEO, and saw som…

Instead of spending time posting stuffs here, could your Googlers get back to your work to improve GCP's quality? Poor availability, of no help customer support, and slow fix of any problems is killing GCP.

Instead of leaving useless comments on the internet, why don’t you join Google and fix those things?

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#728
post #475

Earlier quoted context omitted.

Amazon have been on HN recently for poor customer service with respect to billing for cloud services: https://news.ycombinator.com/item?id=21694835 Google could potentially win by being the least bad not the best.

Poor customer service is not exclusive to Amazon, google directly shut the product down which cannot earn search scale revenue. If you see comments below being downvoted by google PR for examples. I believe all these large cloud companies be it amazon, google or Microsoft deploy army of PR people and campaigns to downvote or try to remove comments which are critical. Especially I have seen this on HN, earlier when I…

I keep seeing you blame any downvote you get on external factors. To me it looks like you're just trying to find excuses and cannot accept that people may be downvoting you for legitimate reasons.

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#729

Earlier quoted context omitted.

Having said that, AWS also have a long track record of reversing charges where a dev fucked up and ran up a huge bill accidentally. I am _extremely_ dubious you'd ever even get a person on the phone to talk to at Google if your CI/CD pipeline or platform automation had a bug that resulted in thousands of dollars of charges racking up over a weekend. I know people who've done that on AWS and had the entire bill waived…

Ah yes the "try getting someone from Google on the phone" trope. I've used GCP at 2 different places. One with a 10k/month spend and another with closer to 200k/month and received the same level of service. In both instances I've had direct access to engineers to get shit fixed when needed, phone/email/gchat.

So if your monthly GCP-spending exceeds the salary of 2 engineers, you get access to at least 1.

Sounds great!

Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud

#730

Earlier quoted context omitted.

> Google's well documented and long history of killing products How long will this tired meme continue to have legs for? Sheesh. Google is not going to shutter GCP right after spending billions of dollars on datacenters and fiber cables. The fact that HN is even entertaining the concept is embarrassing and speaks volumes about fall in the quality of discussion.

What you’re describing is actually the sunken cost fallacy. It’s entirely reasonable to assume Google execs treat the investments as sunken costs that cannot be recovered with GCP, because they rationally should.

Counterpoint, rational Google execs can't keep their jobs after spending 7 years sinking $Bs/year into unrecoverable investments in a product they eventually shutter. Google+ didn't require new physical infrastructure, and the other "Google kills xyz" stories are about small fry stuff.
Post reply on HN