• Maggoty@lemmy.world
    link
    fedilink
    arrow-up
    8
    arrow-down
    7
    ·
    1 day ago

    But why even? There’s no risk to changing it and some risk to keeping it. That’s the reason for the push to change it. Keeping something just because it’s tradition isn’t a good idea outside ceremonies.

    • undefinedValue@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      7 hours ago

      I don’t accept that because everyone’s doing it or “group-think” are valid excuses do jump on a trend. Things like this maybe don’t seem like a big deal for you but for those that hate this culture it’s just one more example of a dumb change being shoved down their throats. This could also be the straw that breaks the camels back.

    • weker01@sh.itjust.works
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      11 hours ago

      There is definitely a risk in changing it. Many automation systems that assume there is a master branch needed to be changed. Something that’s trivial yes but changing a perfectly running system is always a potential risk.

      Also stuff like tutorials and documentation become outdated.

      • Maggoty@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        6 hours ago

        If they can’t change what’s essentially a variable name without issues then should they be doing the job?