• o11c@programming.dev
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    2
    ·
    1 year ago

    The solution is quite simple though: dogfood.

    Developers must test their website on a dialup connection, and on a computer with only 2GB of RAM. Use remote machines for compilation-like tasks.

    • variouslegumes@reddthat.com
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      1
      ·
      1 year ago

      Totally, pretty much all browsers include a way to simulate network conditions. Chrome also includes a way to simulate CPU slowdown.

      • o11c@programming.dev
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 year ago

        and yet the very fact that you have to go out of your way to enable them means people don’t use them like they should.

    • masterspace@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      Server rendered sucks ass. Why would I want to pay for an always running server just to render a webpage when the client’s device is more than capable of doing so?

      Centralization is just pushed because it’s easier for companies to make money off servers.

      • philm@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        You don’t have to render everything on the server, a good hybrid is usually the way to go. Think SEO and initial response. I think lemmy-ui could will also benefit from it (google results)

        • masterspace@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Yeah, it will give you the best of both worlds, but at a fundamental level I still hate that I have to pay for an always running server just for SEO, if I can get away with it I’d much prefer a purely static site that has to have its content pages rebuilt when they change.

      • sznio@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Because it’s better to deliver a page in a single request, than to deliver it in multiple. If you render the page on the client you end up making a lot of requests, each one requiring a round trip and adding more and more delay.