Why is the Google Cloud UI so slow?

Post by cstrahan » Mon, Dec 14, 2020, 7:40 PM UTC

Raymonf wrote: post #325

cstrahan wrote: post #197

Earlier quoted context omitted.

For one, they're using some sort of link / browser history hijacking (something like https://github.com/turbolinks/turbolinks , IIRC) which is buggy, for example: * say you're on page A * navigate to page B * navigate to page C * click your browser's back button, hoping to be back at page B * the github UI screws up and keeps you on the same page while changing the URL in the address bar * so you click back again * n…

What browser are you on? The navigation issues don't happen for me on Chrome.

Post by robertlagrant » Mon, Dec 14, 2020, 8:08 PM UTC

robertlagrant wrote: post #402

sam0x17 wrote: post #232

Earlier quoted context omitted.

On the flipside though, try doing a video chat in Slack.. Not exactly an ideal experience

Agree. But try doing a video call in a channel in a team in Teams, and watch everyone in the team join, not just the people in the channel. At that point you won't miss just starting Zoom so much.

Post by BoiledCabbage » Fri, Dec 18, 2020, 6:37 PM UTC

novok wrote: post #354

allenu wrote: post #314

Earlier quoted context omitted.

This is what I was thinking as well. Once you recognize Conway's Law and Sinofsky's "don't ship the org chart" quote, you start to see it a lot in large companies. Want another great example? If you write iOS apps, you'll probably have worked with the App Store Connect website. That site is such a hodgepodge of slightly different UI paradigms that it could only have been written by multiple teams with differing goals…

I've come to the conclusion that you want to structure your org chart to deliver the structure of application / experience you ultimately want to provide.