5 ms·
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
by jon-wood 6y ago
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.
- alisonkisk 6y agoThis stuff is dead slow even on a fast machine with fast connections. The problem isn't people don't know. The problem is the software is drowning in layers of complexity and abstraction, and it's all in JavaScript not an optimized native language.
- zerkten 6y agoThere can be some more nuance to this. The devs can often see the problems, but know more optimization is needed. They've done everything to implement what a PM asked. 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.
- smueller1234 6y agoThroughout 2020, this hasn't actually been true.