• starry@suppo.fi
    link
    fedilink
    arrow-up
    16
    arrow-down
    2
    ·
    9 months ago

    you have to put in extra work just to make your website not work with privacy measures. like you have to put in the work to use some bloated javascript framework that doesn’t work with noscript instead of just sticking with plain html and css, which would work. on top of that, i’ve encountered way too many big websites that don’t even have a noscript tag so all you see is a ghost layout or a blank page.

    • Kayana@ttrpg.network
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      edit-2
      9 months ago

      That’s something I would disagree with though. “Sticking with plain HTML and CSS” is way more work, and often has significantly less functionality, than building a website with a framework.

      • starry@suppo.fi
        link
        fedilink
        arrow-up
        4
        ·
        9 months ago

        you can build it with a framework, but maybe build it on the server side instead. I’ve seen many nice sites that hardly use any javascript and instead of a bunch of api calls, the server just returns new html to render.

    • ThatFembyWho@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      I don’t mind frameworks, but some features that seem super useful to devs, like google analytics, and various diagnostic/logging tools, social media integrations, I would prefer to “opt in” when I decide they are necessary.