That sounds like a terrible experience. You want to avoid latency spikes at all costs. People might not like latencies as high as 100ms to 200ms but it definitively is possible to enjoy a laggy game like that. Suddenly getting a 500ms latency every minute will cause a lot of weird and unfair situations that can basically ruin the entire game.
The usual latency should be on the order of 30-40ms round trip.
Suddenly getting a 500ms latency every minute
No one said anything about that. The client should have some form of dead reckoning, and there should be an edge server that maintains connections. With the right kind of game mechanics, no one notices the server disappearing then reappearing behind the scenes. I cite 250ms as a worst case. It should be possible to get the impact as low as the server skipping one frame every few minutes. The clients don't need to skip any frames.
I agree, jitter bigger than a synchronization time is worse than high latency. When player have high latency (and I was in top3 on NA Solo ladder in League of Legends while playing from Urals with 220ms), he could only predict the moves of the opponent because what you see is far behind the server state, but with stable latency he knows the exact delay between an input and registering it on the server which puts less pressure to mind to deal with desynchronization between the picture on a display and the actual state.
I agree, jitter bigger than a synchronization time is worse than high latency.
I'll always grant that fast twitch FPS will always have a problem with this. That's not the genre I'm interested in creating games for, and it's not what my server framework is designed to support. (It is real-time action, but the pacing is more akin to RTS than FPS.)
I didn't say that high latency isn't frustrating. But you can effectively shoot the air on the route of the opponent where you'd think he would be by the time server would have your input.
