• whileloop@lemmy.world
    link
    fedilink
    arrow-up
    131
    arrow-down
    1
    ·
    1 year ago

    This could be so much longer.

    Killing children, class systems, so many programming language names, the ridiculous ways equality and order-of-operations are done sometimes. Plenty of recursion jokes to be made. Big O notation. Any other ideas?

      • Hoimo@ani.social
        link
        fedilink
        arrow-up
        42
        ·
        1 year ago

        GOTO is the only thing that makes sense. It’s the “high-level” concepts like for-loops, functions and list comprehension that ruined programming.

        series.append(series[k-1]+series[k-2]) for k in range(2,5)]

        RAVINGS DREAMT UP BY THE UTTERLY DERANGED

        • ChickenLadyLovesLife@lemmy.world
          link
          fedilink
          English
          arrow-up
          15
          ·
          1 year ago

          I started coding with TurboBasic, which included the helpful innovation of GOTO {label} instead of GOTO {line number}, which allowed you to have marginally-better-looking code like:

          GOTO bob

          bob:
          {do some useless shit}
          return

          which meant you essentially had actual, normal methods and you didn’t have to put line numbers in front of everything. The problem was that labels (like variables) could be as long as you wanted them to be, but the compiler only looked at the first two letters. Great fun debugging that sort of nonsense.

        • Vilian@lemmy.ca
          link
          fedilink
          arrow-up
          15
          arrow-down
          1
          ·
          edit-2
          1 year ago

          if goto make sense why don’t you go to get some removed

    • Lightor@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      edit-2
      1 year ago

      Masters and slaves

      Cloning

      Deploying code (that’s what you do with soldiers!!!1)

      Using Git to rewrite history.

      Atomic values (like the bomb!)

      These people are madmen.

      • Gustephan@lemmy.world
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        One of the slave node’s child process failed, so the master node sent a signal to terminate the child and restart the slave

        There’s pretty solid reason my research group is pushing to use “head node and executor nodes” nomenclature rather than the old-school “master node and slave nodes” nomenclature, haha

      • xmunk@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        They always must add up - if they added down then they wouldn’t be floating points now would they!