• Cyyy@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    5
    ·
    7 months ago

    yupp, and i hate that. i use a firefox version that don’t supports private fields, and because a common js lib uses them a lot of websites suddenly stopped working for me just because of this bs. instead of just using a normal variable they use private fields and kill a ton of older browsers by doing so. and most website owners don’t care so asking them just leads to them saying “just upgrade bro”.

        • 0x0@programming.dev
          link
          fedilink
          English
          arrow-up
          4
          ·
          7 months ago

          are implementing more and more forced features you can’t disable

          Not even through about:config?

          • Cyyy@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            7 months ago

            nope, not even with about:config.

            usually it starts with “we let you disable it still with about:config”, but then in later versions they kill it off so the variables don’t do anything anymore. then they remove it completly in even later versions.

    • redcalcium@lemmy.institute
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      private fields

      Man, javascript is starting to turn into java, isn’t it? They added encapsulation. What else they’re going to add?