Re:Mozilla can produce near-native performance on the Web
by carbocation on Wednesday May 22, 2013 @11:16PM
(#5755142)
Quite a few HNers have probably experienced lossy connections such as Amtrak or busy coffee shops. I would think that those high-loss situations would feel somewhat like a high latency experience.
Re:Mozilla can produce near-native performance on the Web
by wslh on Thursday May 23, 2013 @03:56AM
(#5755761)
Lossy mobile connections are very common in the world.
Re:Mozilla can produce near-native performance on the Web
by pyre on Thursday May 23, 2013 @12:50AM
(#5755407)
| DOM manipulation may be absurdly slow however
| it cannot hold a candle to latency hold-ups.
Just an anecdote, but jQueryUI + IE8 took 8 seconds to style all of the buttons[1] we had on a page during one call. Granted, we had a ton of buttons (most were hidden), but that's a lot of time. The same call on Firefox and Chrome were fractions of a second (can't remember the exact numbers, but Chrome was faster at the time), and this was a couple of years ago. DOM manipulation can be a real drag.
Re:Mozilla can produce near-native performance on the Web
by derleth on Thursday May 23, 2013 @12:22AM
(#5755338)
But we do know how to handle bad latency, don't we? Speculative loading, which got a bad name because it makes wallhacks on FPSes work but really has almost no downside once the client can't do anything malicious with a little information the human isn't using yet.
If the real problem isn't latency but bandwidth or bandwidth caps, that will require other solutions.
I would contend that network latency and the plethora of domains queried to be a greater impediment to a speedy web. DOM manipulation may be absurdly slow however it cannot hold a candle to latency hold-ups.
Most readers on HN live in a quiet and peaceful bubble of high-quality network connections, but the majority of the world is beginning to wake up to the web and they'll have to endure latency issues that we haven't experienced since "broadband" was a new concept.