Googlers should be required to develop their apps on 5 year old computers with a network connection capped at 1mbps with 100ms latency. On this flight today I've tried to use Gmail, Google Flights, and Adsense, and they are either ridiculously slow or just don't work.
@aaronpk I actually labbed this type of environment for release testing at a prior employer. Drove the devs nuts, but reminding them they were building this app for their users in mobile environments was important.
And this made our clients very very happy. It also became a key talking point for corporate sales of our service.
@aaronpk Did you know that even though Windows 10 still supports dial-up, it doesn't really work.
The forced basic Telemetry, update checks, internet connectivity pings, etc. alone use up the 56k of bandwidth, so browsing the internet mostly just flat out doesn't work, regardless of patience. If you're lucky, you can get some text content popping up after a minute or two, but even if you wait 15 minutes, most sites are likely to never load a single image unless they're small sub 64x64 pixel icons. 90% of your http requests are simply going to time out or die for other reasons.
They allow YouTube now, so that's not necessarily the traffic pattern anymore.
But my point was that unless you actually have experience running these systems I don't think it's fair to criticize them.
They may be simultaneous connections but you make it sound like a server farm. They are "periodic" demands for upload or download. Maybe 30% of 300 seats are connected, for 90 connections. 10% hit the return key at the same moment, for 9 hits to the uplink at any instance.
I don't think that's fair to say until you've personally had to maintain a wifi network that supports 300 simultaneous connections where the only uplink is an unstable satellite or cellular connection.