Pinging google.com [172.217.5.110] with 32 bytes of data: Reply from 172.217.5.110: bytes=32 time=6ms TTL=50 Reply from 172.217.5.110: bytes=32 time=8ms TTL=50 Reply from 172.217.5.110: bytes=32 time=9ms TTL=50 Reply from 172.217.5.110: bytes=32 time=10ms TTL=50
Ping statistics for google.com: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 10ms, Average = 8ms
I'm on GDC public WiFi.
--- google.com ping statistics --- 12 packets transmitted, 12 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 74.750/75.566/76.724/0.587 ms
I'm on 1GBit Google Fibre in Orange County which should be as ideal an experience as could be expected. Now, considering there would be additional time on top of the pure ping, I image there would be 80-90ms of latency for me. No way lol.
Pretty sure both of us have a Google datacenter nearby, but could the result of your ping be due to a bad configuration on your router?
I could totally make RTS and other real-time games work with that.
Care to share how this tidbit is true?
Lots of filthy casuals just care that they can game. If they can, somehow, why shouldn't they buy the Chromebook? Hell, if that's what they had in school, they might have grown up to like precisely the genres of games that are easy to design around the lag.
Most legit gamers care about input lag
The majority of people don't notice < 40ms round trip lag, though "legit gamers" often do notice. < 30ms, round trip lag, and few people outside of hardcore FPS players will notice. Get to < 20ms, and you get down to rounding error levels. Don't just ask me. (Hobbyist game dev.) Ask gamedevs and companies who have conducted testing.
40ms roundtrip lag for most of the world seems pretty achievable to me.