They were bought by IBM a few years back, but even aside from that they’re a corporation and they care about making money above all else.

It looks like Red Hat is doing its damnedest to consolidate as much power for themselves within the Linux ecosystem.

I don’t think the incessant Fedora shilling is unrelated.

It seems like there isn’t much criticism of the company or their tactics, and I’m curious if any of you think that should change.

  • dgdft@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    21 hours ago

    I do think there are quite a few linux users and developers who are suspicious of Red Hat, they are a small-ish but pretty vocal minority.

    Yeah, I’m with you all the way — no shade to OP, but the question has a flawed premise. I think the majority opinion is that they’re both an asset and a liability. They’re a huge contributor to the ecosystem and have done a lot of practical good, but I also think the community will turn on a dime if the suits overstep into FAFO territory.

    (All that said, fuck Lennart Poettering. Dude couldn’t design a plan to get himself out of a paper bag.)

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      18 hours ago

      Honestly I don’t really see the systemd hate

      Unless they system has less than 64mb of storage I wouldn’t use anything but systemd

      • dgdft@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        6 hours ago

        I appreciate systemd at a high level, and use it all the time, but Nanook’s comment in this thread is dead on the money in my book:

        https://lemmy.world/post/30945123/17510444

        The CLI interfaces for PA and SysD are janky/verbose af and make it hard for beginners to do simple things as well. E.g. try wiring up a virtual device with pacmd that fuses your desktop audio and mic output into a combined source using only the man pages, or putting together a fresh service from memory without looking up any directives.

        E: even better example, compare how easy it is to set something up to run in cron vs. a systemd timer.

        • Dark Arc@social.packetloss.gg
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          There are pros and cons to verbosity and to using many files vs one.

          Cron needs a special tool to edit it because you can break a bunch of stuff trying to edit another, very easily, and by accident.

          The commands themselves when I was first learning I found easier to remember than things like dmesg or /var/log/ … they all follow similar conventions and aren’t so chopped up short that you can’t guess what they do by looking at them.

          Similar to how most people don’t prefer 3 letter variables in code … I’m glad we’ve largely moved on from 3 letter commands. Granted, if you use them a lot you should definitely make your own three letter aliases in your preferred shell scripting language.

    • rumschlumpel@feddit.org
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      20 hours ago

      I don’t disagree with OP at all, though. Just because it’s a minority doesn’t mean they’re wrong.

      • dgdft@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        20 hours ago

        Sorry, bad phrasing on my end. I agree the community should suspicious, but I think the flawed premise in

        It seems like there isn’t much criticism of the company or their tactics, and I’m curious if any of you think that should change.

        is that there is consistent, well-founded criticism and has been this whole time. And even though the vocal folks are a minority, a lot of people feel ambivalent about the relationship rather than viewing it favorably.