Live data from Hacker News

Why is the Google Cloud UI so slow?

debugbear.com

151–160 of 405 posts

Re: Why is the Google Cloud UI so slow?

#151

Earlier quoted context omitted.

yes - it has bad UX and it's broken in Firefox

I don't if this true but I have realized whenever I try to access google apps in firefox they are slow and sometimes breakdown but when I try to do it in chrome they just work fine. Like I was trying to submit some work using google classroom on firefox it wasn't letting me upload the work but when I did it in chrome it just worked well

The conspiracy theorist in me wants to believe that this is not incompetence, but sabotage. Everyone uses Google products; if they work fast in chrome and slow on firefox, people will blame Firefox, not Google. And therefore will eventually switch to Chrome.

Good strategy to steal market share.

Re: Why is the Google Cloud UI so slow?

#152

I think the answer is: This is the best the richest and best companies in the world, with their best paid 100x rockstar developers can do. Google is literally both the creator of the browser (Chrome), the framework (Angular) and the web-app (GCP) we use and still, this mess is the best they can give us. They have direct access to the creators of Chrome and Angular, in some sense they are the owners of the internet an…

Is this some kind of dig against the web? I prefer native myself, but obviously there are huge numbers of faster websites out there.

The answer is that Google’s frameworks suck, and have for many years. I can’t comment on whether things are equally a mess in their proprietary code, but I don’t see any reason to think they’re not. This is a problem with Google, and their slide into mediocrity.

Re: Why is the Google Cloud UI so slow?

#153
I've come to the conclusion it's their way of telling me to use the API or the CLI. As in, why am I throwing all these meabytes of the line just to perform a single command that could be done with the API as well. If only their API wasn't as slow as well.

Re: Why is the Google Cloud UI so slow?

#154
post #150

Earlier quoted context omitted.

Why is everyone assuming that just because someone works for Google has to be competent? Solving algorithmic puzzles is not an indicator or actual technical skills. To me, it looks like a work of incompetent developers led by incompetent technical managers upon requirements of clueless and ignorant product managers.

I think by attributing it do incompetence you're missing the incentives problem. Others point this out, but Google just has no incentives to improve this UX. Think about who makes the decisions to use Google cloud and what criteria they are using. The snappiness of the gcp ui is not likely to be near the top of their list

DigitalOcean built a big business off of easy to use cloud hosting.

Re: Why is the Google Cloud UI so slow?

#155

I think the answer is: This is the best the richest and best companies in the world, with their best paid 100x rockstar developers can do. Google is literally both the creator of the browser (Chrome), the framework (Angular) and the web-app (GCP) we use and still, this mess is the best they can give us. They have direct access to the creators of Chrome and Angular, in some sense they are the owners of the internet an…

I don't think I agree with you here. Make Cloud UI fast is probably not their priority. This is an enterprise product, not consumer facing, users are much less likely to be turned off due to slow UI. They will wait. Integrity/Security would be much higher on the list than UI loading speed. Not surprising at all.

>This is an enterprise product, not consumer facing, users are much less likely to be turned off due to slow UI.

Shouldn't this be the opposite? Maybe this is just me but if I have to use something to do my actual job and it take more time that it should because of the UI I'd look elsewhere.

Re: Why is the Google Cloud UI so slow?

#156
post #5

That's what happens when you employ over-enthusiastic developers obsessed with their Javascript-framework-legacy. Things worked fast when HTML was the UI, and the logic was in the server.

Facebook also makes heavy use of frontend frameworks but all their stuff is fast because they are competent at it.

Re: Why is the Google Cloud UI so slow?

#157

I think the answer is: This is the best the richest and best companies in the world, with their best paid 100x rockstar developers can do. Google is literally both the creator of the browser (Chrome), the framework (Angular) and the web-app (GCP) we use and still, this mess is the best they can give us. They have direct access to the creators of Chrome and Angular, in some sense they are the owners of the internet an…

I don't think I agree with you here. Make Cloud UI fast is probably not their priority. This is an enterprise product, not consumer facing, users are much less likely to be turned off due to slow UI. They will wait. Integrity/Security would be much higher on the list than UI loading speed. Not surprising at all.

The UI is the primary management interface, log search interface, and in certain cases, analytics interface.

Re: Why is the Google Cloud UI so slow?

#158
youtube is the same slowwwwwwwwwwwwwwww loading experience, it really shows when you try to use it on an underpowered chromebook.

It's strange to me that google devs don't dogfood their own google branded products! They just assume everyone is using the same dev workstation they are?

Re: Why is the Google Cloud UI so slow?

#159

I think the answer is: This is the best the richest and best companies in the world, with their best paid 100x rockstar developers can do. Google is literally both the creator of the browser (Chrome), the framework (Angular) and the web-app (GCP) we use and still, this mess is the best they can give us. They have direct access to the creators of Chrome and Angular, in some sense they are the owners of the internet an…

I think the UI is probably not a high priority on their side and they assign most of the work to juniors and outsourced.

Re: Why is the Google Cloud UI so slow?

#160
post #44
post #39

Earlier quoted context omitted.

As a developer you should 1) have the fastest possible code / test cycle - i.e. it's worth overpaying for faster machines 2) treat performance as a feature and formally measure it across configurations

I've worked for many companies, small and large, corporate and startups. None of them had performance as a priority, or even considered at the product level. Any minimal performance optimization or win we had was because a developer cared enough for it.... but maybe I'm the only one and just had bad luck with the product managers/owners I had.

The only companies I have worked for that really cared for performance were betting companies, because speed is money in that sector (esp. in live betting).
Post reply on HN