Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

theinformation.com

Post reply on HN
Print view View original

691–700 of 856 posts

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

#691

Post by jboy55 »

altgoogler wrote: post #414

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…

I will believe Google is serious about supporting GCP when they decide the job of interacting with their customers and partners is worthy of being labeled a 'Googler'.

Since it seems the majority of support and service at Google Cloud is made up of TVCs, with 2 year 'life spans', it seems Google is just hedging their bet, no need to bring people on permanently if you're going to downsize in 2-3 years. In fact, is it entirely coincidental that the goal is to be #1 in roughly the same timeframe as the TVCs are allowed to work? Seems like the same sort of lack of commitment to GCP that Google place in their workers.

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

#692

Post by ec109685 »

antoncohen wrote: post #286

I want to put on end to the "you can't contact Google" comments that comes up every time Google Cloud makes the front page. You can contact Google Cloud. They are very responsive. I'm currently at a small startup using GCP, and I've been at similarly sized startups with equivalent AWS spends. I have found it easier to have serious discussions with GCP, compared to AWS. We have dedicated GCP contacts. We actually have…

With Slack, anyone in the organization can file a ticket and get a human to respond in a few hours. If something isn’t great about Google Sheets (or of their cloud offerings), I have no idea how to submit and issue that will get attention of someone at google. They lose big time for this stance.

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

#693

Post by ec109685 »

prepend wrote: post #350
Touche wrote: post #296

Earlier quoted context omitted.

Who is the internal competitor to Google Cloud?

I don’t think Google internally uses GCP. So a direct competitor would be whoever runs the “real” google cloud that all the internal stuff.

Good point. Google using GCP internally would be strong validation of the product and I think add more comfort for enterprising adopting it.

E.g. what coup would be for Google Search to run on GCP. Imagine the CIO conversation of, “well, if it is good enough for google search, it must be good for me”.

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

#694

Post by richardw »

altgoogler wrote: post #414

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…

Betting on Google’s offering is like betting your business on Bing. It might work but it’s an also-ran. And that’s before this leak. Time for leadership to clarify hard, ASAP.

Infrastructure should be built on rock, not sand. Google has sold too much sand.

Businesses need to focus on their next battle not finding a replacement API, web toolkit or cloud.

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

#695

Post by dragonwriter »

This whole story seems weird and inconsistent, but particularly: “The pressure to show more progress very soon in the business extends to Google Cloud product teams, which the company is now asking to develop detailed multiyear strategic plans, a former Google Cloud employee said.”

Detailed multi-year strategic planning as a change from 18-month plans seems more consistent with a recognition that significant progress on the obvious indicators is a long slog and that positioning for it is going to take tracking less direct indicators over a longer period than it is with increased pressure for short-term results. Increased pressure for immediate results tends to be accompanied by reduced long-term planning.

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

#696

Post by dragonwriter »

BurritoAlPastor wrote: post #678
res0nat0r wrote: post #672

Earlier quoted context omitted.

The issue is that folks here think GCP is the same thing as Google Reader. That's absurd. Google is currently building a massive $500 million datacenter outside of Reno as we speak, and has 10+ billion invested in their datacenter cloud offering buildout this year alone. GCP and the entire physical infrastructure isn't going to get "turned off" if it isn't #1 in the market in 3 years, that's just silly. https://9to5g…

Agreed that Google isn’t going to announce one day that they’re going to demolish all the datacenters in 30 days, but that doesn’t mean that GCP has any guaranteed future either. If Google leadership decides to walk away from cloud hosting, it’ll come in the form of reallocated engineers, reduced headcount, smaller conferences, and a general transition to “maintenance mode”. (At which point it’s a corporate backwater…

> that doesn’t mean that GCP has any guaranteed future either.

Nothing has a guaranteed future.

> AWS and Azure won’t slow down development

As long as it's paying off, they won't, and AWS maybe for longer even if it isn't. But Microsoft is no stranger to making investments in offerings and letting them stagnate or outright killing them if they don't pay off.

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

#697

Post by [deleted] »

scarejunba wrote: post #564
jacquesm wrote: post #561

Earlier quoted context omitted.

Funny thing about plus, reader and wave: that was the kind of stuff that people who are now in positions to make infrastructure decisions got worked up about. It's the sort of image damage that may have seemed minor and acceptable at the time that can come back with a very large multiplier in the future, especially given the kind of prominence those products once had.

This was genuinely not a factor when we signed a 1E8 deal with GCP. What was a factor: (non-exhaustive) * Access to their developers for core services * Discounts available * Quality of support * Access Controls / Audit / Budgeting * Dev Tools around Infra * Future Roadmap Not one of us ever would have chosen the shutdown of Plus/Reader/Wave as a factor. As a startup we hard pivoted in order to succeed. No surprise t…

[deleted]

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

#698

Post by MatthewKernerMS »

jiggawatts wrote: post #362
rzmnzm wrote: post #211

Earlier quoted context omitted.

Azure has a pretty nice tech stack in my experience, what issues are you experiencing with it?

There's a laundry list. The resource template format is inhuman gibberish designed for machines. It does idiotic things like manually hard-coding enums in the template to support drop-downs. This means templates go "stale" very quickly and are super fiddly to update to support things like new VM sizes. You cannot export resource groups bigger than a certain size, so if some idiot in your org makes them too big, there…

Thanks much for providing specific feedback on areas where Azure could do better. This is really helpful and I've followed up with owners for the components you mentioned. None of these points fall directly into areas that I work on, but I'll make sure teams are aware.

I did want to correct one misconception, which is that we do not outsource Azure product development (we do, from time to time, hire contractors to add force on projects, but these projects are led by FTEs who are involved on a daily basis). There are certainly areas where we strive to target lean MVPs so we can get new products into customers' hands faster and get feedback earlier. I'm sure there will be some sharp edges there and we greatly appreciate you giving these services a try.

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

#699

Post by MatthewKernerMS »

jiggawatts wrote: post #669
fatbird wrote: post #456

Earlier quoted context omitted.

To change the vnet of a VM, you still need to deallocate it and restore it into the new vnet. Anything they don't offer directly, they offer a pile of canned VMs authored by Bitnami, who adds their own layer of management scripts to them, which (in our case) corrupted the filesystem on restarting from the great Shellshock cloud reboot. Azure is, in part, an ad-hoc cloud offering made up of services offered by mutuall…

Just to add to my previous post... this is stuff that has irritated me in just the last few minutes : * When selecting a VM size in the new-VM wizard, it silently resets it to "DS1 v2" a bit later. You have to go back to the first tab and re-select the size you really wanted. * This then promptly resets my "Already have a Windows Server license?" setting so then I have reapply that too . * The default VM template sug…

As above, I've shared these points as well with teams who own these areas. Thanks again!

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

#700

Post by MatthewKernerMS »

fatbird wrote: post #456
jiggawatts wrote: post #362

Earlier quoted context omitted.

There's a laundry list. The resource template format is inhuman gibberish designed for machines. It does idiotic things like manually hard-coding enums in the template to support drop-downs. This means templates go "stale" very quickly and are super fiddly to update to support things like new VM sizes. You cannot export resource groups bigger than a certain size, so if some idiot in your org makes them too big, there…

To change the vnet of a VM, you still need to deallocate it and restore it into the new vnet. Anything they don't offer directly, they offer a pile of canned VMs authored by Bitnami, who adds their own layer of management scripts to them, which (in our case) corrupted the filesystem on restarting from the great Shellshock cloud reboot. Azure is, in part, an ad-hoc cloud offering made up of services offered by mutuall…

Thanks very much for the product feedback. I've routed the points of feedback to the teams who own the components involved to take a look.
Post reply on HN