1. 65

  2. 10

    My hometown still doesn’t have anything better than 56k, and every time I go home I’m reminded of this painful fact. You’d think that companies would realize that they’re losing users by adding that extra JS framework, but maybe that’s all a part of their calculated cost.

    1. 2

      Forget 56k, web developers should be made to dogfood the fruits of their labour using serviced office (Regus/WeWork/TOG/etc) Internet connections. Even in central London it is the accepted norm for the connectivity to be plain awful. Having had to myself setup in a shared office, you cannot get your own circuit installed without being charged a corkage fee which just so happens to be the same price as their own Internet offering.

      Sure, I can believe they have provisioned a ‘10Mbps circuit’ but when it is contended at 50:1 with every other company in that shared location…at least your 56k modem gives you a steady and predictable 6kB/s :)

    2. 7

      A lot of it is also quite unusable if you have a “slow” computer. Some things I can only really use on my expensive work laptop, not on anything I purchased myself. It makes me sad, because it seems in opposition of core values of the web.

      1. 5

        This is in part why I’ve been opposed to gratuitous or unnecessary uses of JavaScript. It makes the browser a real dog.

      2. 6

        Most of the web still sucks if you have a fast connection.

        1. 6

          Unfortunately the reality is that most websites is not designed for slow connections. This is the same for users who have outdated browsers as well as those who disable java script. When devs tell managers that X doesn’t work for Y browser, or doesn’t have full compatibility, managers will see that it will take ZZZ hours for an issue that affects 2% of users.

          1. 3

            I dont have much pity left for outdated browsers.., though there are always exceptions

          2. 4

            I was wondering how blog.codinghorror.com could be so heavy and it’s basically all high-res pictures. Some issues on web page sizes are about Web 3.0 and devs wanting to write apps in the browsers, but sometimes devs just don’t follow best practices.