• 0 Posts
  • 7 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle

  • True, Linux did solve this decades ago. And then made it significantly worse in the last decade with multiple package managers (apt-get, AppImage, Flatpak, Snap, brew, random .sh install scripts etc.). Remembering how a Linux application was installed and calling its update command is a chore, and updating will probably pull in some other 500MB+ dependency that’s not shared with other apps because of a minor version change.

    If your distro is forcing you to use more than one package manager on a regular basis, you need to switch distros.

    If you’re choosing to use 3-4 package managers simultaneously, even though you don’t really need to, that’s on you.

    Either way, it isn’t Linux’s fault.


  • nyan@lemmy.cafetoLinux@programming.devInit Systems
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 days ago

    systemd is a monolith in practice, despite what its advocates like to claim. You can’t run just a part of it under another init without doing extra patch-up work (see elogind). Whereas you can run just one GNU utility on top of, or even alongside, someone else’s implementation of that or other utilities (for instance, in parallel with a rust implementation that isn’t quite ready for the big time yet).

    systemd also won’t work on anything except Linux. Older solutions also worked on BSD. That matters to some people.

    And the issue was never just Poettering’s employers. He had a bad reputation in parts of the Linux community long before systemd—he was also the main force behind pulseaudio, which was shipped long before it was ready for actual use in the real world and remained in a semi-broken state for quite a long time afterwards. And he often comes across as personally obnoxious. Nothing like telling someone “I’m not interested in fixing your issues with my project” (except less politely) to get them to adopt your code.