• Go-On-A-Steam-Train
    link
    fedilink
    150 minutes ago

    Hmm…this has me thinking, maybe I’ll change up my Hugo site a little, so that there’s no dropdown menu - it’s the only thing javascript is needed for.

    Thank you for this, some points that I’d not even considered, and a helpful reminder to myself to try and get that javascript from 99% to 100% unused. :)

  • @Vincent@feddit.nl
    link
    fedilink
    83 hours ago

    Note there’s a group of users that larger than the group of users without JS (for whatever reason): users of assistive technology. And they don’t even have a choice.

    While I’m all for considering the needs of every user… If you get to the point where you’re worrying about no-JS users, I hope you’ve already considered the needs of people with disabilities, whether temporary or permanent.

    • @ozr@programming.dev
      link
      fedilink
      3
      edit-2
      34 minutes ago

      No-JS pages that fully comply with WAI ARIA are much better for users of assistive technology than any single page web app can ever hope to be. All the myriad states that an interactive JS page can enter are absolutely never ever properly tested for disabled users, and even after full expensive testing, just a little change in the JS can ruin it all again. While with WAI ARIA you can just quickly assert that the page is compliant with a checker before pushing it to live.

    • @Static_Rocket@lemmy.world
      link
      fedilink
      English
      32 hours ago

      Doesn’t avoiding JS typically structure a website in such a way that the browsers built-in assistive services can cover it easier?

  • @MonkderVierte@lemmy.ml
    link
    fedilink
    22 hours ago

    People should not be prioritizing no-JS users. No one turns off JavaScript.

    If you keep the JS to a minmum, you have

    1. less work maintining that shit, HTML/CSS is patient
    2. better user experience

    So much forms and textboxes don’t save content anymore after a reload, because it’s dynamically loaded from somewhere or even a <div> frame handled entirely by JS. Buttons/Checkboxes that don’t work, it’s sad.

  • @SpicyLizards@reddthat.com
    link
    fedilink
    157 hours ago

    Sadly, the rise of frameworks and SAAS have really killed security and accessibility through enforcement of JS.

    ‘Back in the day’ performance, download size, backwards compatibility, and non-js functionality was expected. Now it’s not even on the radar for most big corps/agencies. Many places I’ve worked don’t even care about responsiveness, which is crazy.

    Now, there are so many 25mb websites that are unusable without JS or the right device…

  • Aatube
    link
    fedilink
    268 hours ago

    The point is: a lot of people browsing your site will at least temporarily have a no-JS experience without intentionally doing so.

    💯

  • @tauren@lemm.ee
    link
    fedilink
    English
    -12 hours ago

    A lot of people who shared this sentiment were hung up on the idea that “no one turns off JS.” But some people do, for a variety of good reasons!

    What % are we talking about? 50%, 25%, 10%, 1%, 0.1%? People make choices, but those are their choices. I need to get the job done and I can’t cater to everyone’s needs.

  • @PunkRockSportsFan
    link
    English
    3610 hours ago

    JavaScript sucks. I hate using it I hate coding it.

    I whitelist js sources on my personal computer.

    Only absolutely necessary for function scripts get loaded.

    If they ask me to disable the adblocker I blacklist the domain.

    • mesa
      link
      fedilink
      English
      27
      edit-2
      10 hours ago

      I’ve done more than 18 years of dev work. I only hate js. All the other parts of the job are fine. Other languages are fine as well. I’ve had to learn so many. Hell I know cobol right along side ruby.

      Js sucks. It sucks to debug. Its frameworks still have issues with basic stuff like many to many relationships.

      All the solutions that don’t use or use it sparingly work for years. The ones that rely on the language usually die a firey death by npm/yarn or get deprecated within 6 months.

      • Zos_Kia
        link
        fedilink
        147 minutes ago

        Its frameworks still have issues with basic stuff like many to many relationships.

        Not sure what you mean by that. Do you mean ORMs? Which one and when did you try it?

      • @PunkRockSportsFan
        link
        English
        1510 hours ago

        Js frameworks make php frameworks seems stable efficient and logical by comparison.

        Yikes.

        • mesa
          link
          fedilink
          English
          89 hours ago

          Modern day php and laravel is actually not terrible.

          But yeah I agree with you.

    • @jjjalljs@ttrpg.network
      link
      fedilink
      36 hours ago

      Javascript is like Dungeons and dragons. It’s a mess, weighed down by legacy decisions, too heavy in some places and too light in others, and used in far more places than it should be. It also has some diehard fans, and some diehard fans who have never used anything else.