wow just wow while i can’t say i didn’t see this one coming but it always amazes me where greed could lead someone

    • static@midwest.social
      link
      fedilink
      English
      arrow-up
      34
      arrow-down
      2
      ·
      1 year ago

      The best reasoning I saw for this change was for clarity for non native English speakers. If you’re learning the language “allowlist” is definitely more clear in meaning than “whitelist”

        • 3laws@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          1 year ago

          I don’t know what you are talking about.

          Even if our dialects (Mexican) didn’t have vestigial racism and fake dichotomies, permitir y bloquear is as straight forward as you can get.

          IT switched from white/black literally years ago, if your department didn’t, you are quite stuck in time.

    • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
      link
      fedilink
      English
      arrow-up
      27
      arrow-down
      6
      ·
      1 year ago

      A lot of companies seem to be doing this, personally I think trying to make a connection between race and tech is a bit far fetched. Nobody thinks of race when talking about whitelists and blacklists…

      In public repos where these changes are merged in to FOSS projects, they get little resistance too - although I could see concern of a potential backlash if anyone questioned the alleged benefit of such a change.

      Imagine if this approach was taken with the (now outdated) IDE interface? Instead of “Primary Master, Primary Slave, Secondary Master, Secondary Slave”, there’d maybe be “Primary Primary, Primary Secondary, Secondary Primary, Secondary Secondary” 😵‍

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

      My company has recently started disallowing these words in code. The funny part though is the first few lines of the Jenkins job responsible for checking this stuff proudly states “Waiting for slave node to start checks.”

      I know it’s a minor fix in the jenkinsfile but I chuckle every time I see it.