Atlassian Jira is dog slow too. Drives me nuts.
If you're on a mac try the jira app from the appstore, it's much, much faster.
Why is the Google Cloud UI so slow?
61–70 of 405 posts
Re: Why is the Google Cloud UI so slow?
#62Re: Why is the Google Cloud UI so slow?
#63User to Dev: the memory usage is excessive. Dev with 256 GB RAM to User: WFM I would not be surprised if a lot of these problems could be traced back to developers having above-average network connections and super beefy computers. Combine that with fresh or minimal installs while testing the software, without lots of data that accumulated over month or years of use and in consequence they experience their products a…
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.
GCP's UI? Yea it's pretty bad. GCP's terraform provider? It's really slick. Probably the best one of the bunch (Azure, AWS, Oracle, OVH, ...).
Re: Why is the Google Cloud UI so slow?
#64Earlier quoted context omitted.
I don't think it is just that. Google is just shockingly bad at web frontend. All their properties are terrible, except maybe Youtube which I find quite agreeable. For example I just made a search on google.com, the most popular website in the world, and it can't even fit the content into this reasonably sized window [1]. [1] https://i.imgur.com/ER5yfbd.png
Try not using an esoteric desktop environment and web browser.
Re: Why is the Google Cloud UI so slow?
#65Earlier quoted context omitted.
I don't think it is just that. Google is just shockingly bad at web frontend. All their properties are terrible, except maybe Youtube which I find quite agreeable. For example I just made a search on google.com, the most popular website in the world, and it can't even fit the content into this reasonably sized window [1]. [1] https://i.imgur.com/ER5yfbd.png
Try not using an esoteric desktop environment and web browser.
Re: Why is the Google Cloud UI so slow?
#66Re: Why is the Google Cloud UI so slow?
#67My pet peeve is that a lot of the GCP console doesn't even seem to work in Firefox. For example: https://github.com/webcompat/web-bugs/issues/61522
This is one of the first features a new GCE user is likely to use (if they're exploring the UI and haven't yet started using the CLI) - and it's broken out of the box. Amazing.
It's amateur hour over there when it comes to frontend development - it's not a web app where cross-platform/cross-browser testing takes place, it's a Chrome app.
Re: Why is the Google Cloud UI so slow?
#68Re: Why is the Google Cloud UI so slow?
#69Google's UI's in general are shockingly slow. I don't understand why my Google Drive and Gmail have input lag and choppy animations on my 5 year old xps13, it's not that hard to make navigating a filesystem or list of emails fast. Actually I do understand, it's because they want everything they build to be made in a massive javascript framework with shared components, which looks nice but runs like garbage on anythin…
Re: Why is the Google Cloud UI so slow?
#70User to Dev: the memory usage is excessive. Dev with 256 GB RAM to User: WFM I would not be surprised if a lot of these problems could be traced back to developers having above-average network connections and super beefy computers. Combine that with fresh or minimal installs while testing the software, without lots of data that accumulated over month or years of use and in consequence they experience their products a…
I suspect there's something in that comment on above-average network connections - the people working on Google Cloud's UI are going to be doing so from Google networks, or over a Google VPN, which means they'll be seeing much lower latency to your average person who has to be bounced around their ISP network and then across a couple of peering providers before getting there.
When the PM views it with ideal network conditions they assume it's more than ready. At this point their focus is on shipping sooner so the next thing can be worked on. The devs can never talk them back. Users then complain on Twitter about the crappy perf.
This is a process and cultural failure too. The perf can be quantified and tracked to some extent. Even proxy metrics like the growth of assets over time can help.
Cultural events like poor handling of weekly demo days can create undue pressure on shipping poor implementations. Someone implements a great idea badly, it catches management attention (or helps the sales team), and next Monday it gets released. Over time this behavior can hurt customers and it always frustrates internal efforts to do the right things for perf.