• @Cyyy
    link
    English
    09 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”.

    • @gaylord_fartmaster
      link
      English
      59 months ago

      Why? I feel like a browser is something you’d definitely want to keep up to date for security reasons if given the option.

      • @Cyyy
        link
        English
        -6
        edit-2
        9 months ago

        deleted by creator

        • @[email protected]
          link
          fedilink
          English
          49 months ago

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

          Not even through about:config?

          • @Cyyy
            link
            English
            2
            edit-2
            9 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.

    • @[email protected]
      link
      fedilink
      English
      19 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?