Earlier quoted context omitted.
He mentions packet loss of 10%. That's a different problem than a slow connection.
High packet loss and slow connections frequently go hand in hand (TCP over cellular modems). This effect is exacerbated if the web site you're connecting to changes congestion control and TCP ramp up settings.
The web sucks if you have a slow connection
231–240 of 622 posts
Re: The web sucks if you have a slow connection
#232Something that sticks out looking at the table. How can some sites simply FAIL loading? I mean, there is something inherently wrong with our web today, where if my internet is very slow and _could_ load a page in 80 seconds if I just leave it like that, the server itself could have configured the timeout to be 60 seconds. So I can never load the page?! The assumption is here that both points of the connection is base…
I chatted about just this timeout issue with an engineer from a major CDN while he was at my house enjoying the dialup. Seems like simply a matter of resource management; slow connections do use more resources. Most CDN customers don't care or don't know that a few percent of the US population is getting their web browsing broken by timeouts, so there's no push back. (NASA has their wacky ways around the issue for IS…
Re: The web sucks if you have a slow connection
#233Something that sticks out looking at the table. How can some sites simply FAIL loading? I mean, there is something inherently wrong with our web today, where if my internet is very slow and _could_ load a page in 80 seconds if I just leave it like that, the server itself could have configured the timeout to be 60 seconds. So I can never load the page?! The assumption is here that both points of the connection is base…
Re: The web sucks if you have a slow connection
#234Earlier quoted context omitted.
This was the baseline experience everywhere in the 90s: people would just do something else while they waited for things to download over dialup. Clients for things like email, Usenet, browsers, etc. commonly had batch modes where you could queue large downloads so you could basically see what's new, select a bunch of large things, and then let it download while you got a cup of coffee / dinner / slept.
Not sure what your comment has to do with mine. I used Internet in the 90s and dial-up specifically as recently as 2004 - and have quite a good memory of the experience. Internet at dial-up speed was an extremely valuable commodity, to the point of disabling images in the browser and only downloading the most essential things (which is about as far from a youtube video you can get) - like documents and zipped install…
Someone doesn't agree with your comment, but rather than come back with a refutation they voted you down instead :)
And someone else don't agree with my comment .. modded down -4
Re: The web sucks if you have a slow connection
#235Earlier quoted context omitted.
Incidentally, you may find GMail's "basic HTML view" works better when your connection's throttled: https://support.google.com/mail/answer/15049 And as for reddit, their old mobile view is still available at the "i." subdomain - it's so much lighter-weight than the dreadful JS-laden one they introduced a while back, it's the only way to use reddit on mobile IMO: https://i.reddit.com
It's a shame that their oldest mobile version, the original m.reddit.com is no longer available. It was truly the most compact way to experience the site. Barely more than a list of links.
Re: The web sucks if you have a slow connection
#236Re: The web sucks if you have a slow connection
#237>When I was at Google, someone told me a story about a time that “they” completed a big optimization push only to find that measured page load times increased. When they dug into the data, they found that the reason load times had increased was that they got a lot more traffic from Africa after doing the optimizations. The team’s product went from being unusable for people with slow connections to usable, which cause…
Hah! A Jevons Effect[1] in a web site's bandwidth! [1] When an increase in the efficiency with which a resource is used causes total usage to increase. https://en.wikipedia.org/wiki/Jevons_paradox
Re: The web sucks if you have a slow connection
#238Earlier quoted context omitted.
One wonders how a user that takes 2 minutes to load 98KB is actually able to watch a video. Even by the most optimistic estimations, a video that is a few minutes long at 480p will weigh in at 10 megabytes, meaning it'll take them OVER 3 HOURS to download the entire thing. You would probably be able to browse (slowly), read comments, but not actually do much else.
I'm guessing you've never downloaded porn from usenet over a 2400 baud modem.
Re: The web sucks if you have a slow connection
#239Ssh into a shell account and use a text based browser :)
Re: The web sucks if you have a slow connection
#240Something I have had at the back of my mind for a long time: in 2017, what's the correct way to present optional resources that will improve the experience of users on fast/uncapped connections, but that user agents on slow/capped connections can safely ignore? Like hi-res hero images, or video backgrounds, etc. Every time a similar question is posed on HN, someone says "If the assets aren't needed, don't serve them…
Like another reply to your comment, I thought about having a very small js script in the header puting `Date.now()` in a global, then on page load, having another script checking the amount of time that had passed to see if it was worth downloading the "extra" at all. But then again where do you put the threshold? Has anyone tried this with some degree of success?