• @Ramenator
      link
      221 year ago

      “Dammit, for some reason I can’t kill all the children, a few of them always survive, I must have a leak somewhere”

    • meow
      link
      fedilink
      61 year ago

      I think that’s why we’re supposed to call it main now

      • Kogasa
        link
        fedilink
        91 year ago

        “master” in version control has no corresponding “slave,” but nevertheless the “master/slave” terminology is the reason why GitHub switched to “main” and everyone else followed suit

      • @[email protected]
        link
        fedilink
        21 year ago

        The naming isn’t great still… I usually use ReadWrite instance and replica. I really wish we had some more concise replacement terms.

        • Kogasa
          link
          fedilink
          71 year ago

          Main is the replacement for master for git branches, not the general master-slave pattern. Wikipedia suggests:

          Other replacement names include controller, default, director, host, initiator, leader, manager, primary, principal, root; and for slave: agent, client, device, performer, peripheral, replica, responder, satellite, secondary, subordinate, and worker.

          I usually use controller / worker if it’s a local process or controller / remote if the subordinates are on different hosts.

          • @[email protected]
            link
            fedilink
            11 year ago

            I know I’m old, but never found that calling a dumb machine a slave to be problemtic. The thing is supposed to obey my orders. It’s in the code and code is law.

            I’m also not American and never owned slaves.

  • @[email protected]
    link
    fedilink
    English
    41 year ago

    Naming things is hard and people really suck at it. Many new projects just pick a random word out of the dictionary (or encyclopedia) that has absolutely nothing to do with the project or company and mess up internet searches forever.

    The game “Brand name or dictionary entry” would probably be very difficult to play.

    CC BY-NC-SA 4.0

    • AggressivelyPassive
      link
      fedilink
      31 year ago

      That’s why I chose random first names for my internal toy projects at work.

      Worked great, until I found out, that a pretty stupidly named tool is now kind of a cornerstone and its name was thrown around in conversations with the upper management.

  • Lung
    link
    31 year ago

    Potato salad

  • Andrew
    link
    fedilink
    11 year ago

    *non-windows-fans /s

    (I hate C# and I hate .Net)

    • Kogasa
      link
      fedilink
      61 year ago

      .NET Core is highly multiplatform. Windows still gets preferential treatment but there are few obstacles to .NET development on Linux. It’s a nice ecosystem that’s increasingly open source. All that said, obligatory fuck Microsoft.

      • Andrew
        link
        fedilink
        -4
        edit-2
        1 year ago

        All this multiplatform stuff is bullshit according to my experience. The dotnet CLI is slow, files still use CRLF line ending, I also remember CLI autocompletion was not great. C# has only one working LSP server implementation that sucked ass in VS Code and Neovim. It’s kinda like Java DX, but at least with Java the DX is equally isn’t great on any OS. Maybe I like C# more than Java as a language, but I hate everything else. I also hate Java, btw.

        Also .Net wasn’t always OSS, therefore it has proprietary history (Java has less of the same).