Initially the bug report was shot down by systemd developer Luca Boccassi of Microsoft with:

So an option that is literally documented as saying “all files and directories created by a tmpfiles.d/ entry will be deleted”, that you knew nothing about, sounded like a “good idea”? Did you even go and look what tmpfiles.d entries you had beforehand?

Maybe don’t just run random commands that you know nothing about, while ignoring what the documentation tells you? Just a thought eh"

Good devs, good product, I’m really excited about out shitty, shitty future.

  • Technus@lemmy.zip
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    Someone should force this guy to read about the principle of least astonishment.

    Doesn’t surprise me that a developer from Microsoft doesn’t understand this. To this day, when I select “Update and Shut Down” in Windows, it only actually shuts the computer down about half the time.

    • thingsiplay@beehaw.org
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      To this day, when I select “Update and Shut Down” in Windows, it only actually shuts the computer down about half the time.

      And that surprises you?

      • Technus@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        At this point, no. But it’s still incredibly annoying and a little spooky when I’m laying in bed and I see my computer screen light up in the next room when it’s not supposed to.

        It’ll even wake itself from sleep when it wants to update, but it won’t start it automatically, I think because it hits the lock screen.

        I’ll probably try Linux on ir when Windows 10 hits EOL.

    • Bookmeat@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      Hey, it’s better than the gnome developers who will just close your issue when the discussion gets “too heated” or they refuse to see your use case as valid.

        • perishthethought@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 months ago

          Yah, if a developer wants to call all/most of his users ‘idiots’, they should have someone else interact with users.

          • Technus@lemmy.zip
            link
            fedilink
            arrow-up
            0
            ·
            5 months ago

            Wanting to and actually doing it are two different things.

            The problem is that open source devs also have to be their own project managers, but those two jobs have very different skillsets.

            In regular software development, it’s the PM’s job to deal with the drama, filter the idiocy out and collect concise and actionable user stories, and let the developers just write code.

            In open source, you tend to deal with a lot of entitlement. All kinds of people, who never gave you a dime, come out out of the woodwork to yell at you over every little change. The bigger and farther reaching a project is, the more this happens, and it wears you down. I can only imagine what it’s like working on a huge project like GNOME.

            And the toxicity feeds into itself. Be kurt with one person, and suddenly it gets out that you’re an asshole to users. Then people come in expecting hostility and react defensively to every little comment. And that puts you in the same mindset.

            At the end of the day, you can’t satisfy everyone. Sometimes you gotta figure out how to tell someone their feature request is stupid and you’re not gonna work on it, especially not for free. And a lot of people need to learn to try to fix problems themselves before opening an issue. That’s kind of the whole point of open source.

    • Exec@pawb.social
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      Doesn’t surprise me that a developer from Microsoft doesn’t understand this. To this day, when I select “Update and Shut Down” in Windows, it only actually shuts the computer down about half the time.

      There are some tasks that only can be done when the majority of the system is not in use. Windows prepares the files, reboots, does its thing in a preboot environment, then it actually shuts down.