Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:37:10 JST Rich Felker

   The level to which systemd stans demand you prove claims against systemd that you didn't even make as soon as they see you say something they interpret as vaguely "anti-systemd" is really astounding and impressive.

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:37:08 JST Rich Felker

     in reply to

     • Irenes (many)

     @irenes At least 75% of my objection to systemd is governance & unilateral imposition of policy.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Irenes (many) (irenes@mastodon.social)'s status on Wednesday, 06-Mar-2024 23:37:09 JST Irenes (many)

     in reply to

     @dalias right, like, the really frustrating thing is that we like almost all of systemd's architectural decisions... and we do believe there need to be more people paying attention to overall ecosystem health stuff with Linux... but we don't like the clear hegemonic intent. BDFL is not an appropriate governance structure for something with this scope.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:38:08 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito I don't want the softwares I'm running talking to each other. I want their behaviors to be predictable, tractable to mentally model, independent of what else I have installed/running. I want principle of least surprise. I don't want weird actions happening because I happened to plug in thing X and software Y that was running is interested in that. I don't want privacy spills from what I was doing in one app showing up in another. ...

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:38:11 JST Raito Bezarius

     in reply to

     @dalias Fair enough, be it related to dbus or tight coupling, I am afraid I am still unable to grasp what point you are articulating *concretely* with that. I see mostly theoretical concern, not grounded in modern and actual blockers you might have encountered because I still cannot derive a concrete instantiation of what you are saying, applicable to objects I am familiar with.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:38:12 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito The only comment I made here about "user-hostile behavior" was in a subthread about dbus and tight coupling and my observations of the philosophy it developed out of, going back to the early 1990s. It's barely even related to systemd.

     I could make "user hostility" complaints about systemd but that's not what I came to do because I've really gotten tired of that topic.

   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:38:14 JST Raito Bezarius

     in reply to

     @dalias What I find fascinating is that the discussion always goes like this and I am still unable to find a satisfying understanding of that behavior beyond different tastes and colors and a strange feeling of reading FUD (about user hostile behavior).

     But I would be glad to understand that I am completely wrong and missing the point and actually the problem is **concretely** X, Y, Z.

   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:38:16 JST Raito Bezarius

     in reply to

     @dalias I maintain a distribution that probably exercises more code of systemd than any other distribution out there, it's not beautiful, there's a lot of issues but what I don't really understand after dealing with the alternatives is that other people seemingly *not involved* into working with the object of interest doing weird over-intellectualization of system design to discuss abstract problems related to that ecosystem.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:40:26 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito "Imposition of policy" was in a completely unrelated thread that has nothing to do with this.

     It still sounds like you have stuck in your mind that this is supposed to be some sort of indictment of systemd that you're supposed to "accept as criticism". That is totally not the point.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:40:27 JST Raito Bezarius

     in reply to

     @dalias OK, that's fair. Nonetheless, I must point out that both philosophies have produced different results, whether you find that user hostile seems to depend on your definition of user (for example, you but not me). You talked about "imposition of policy" in another thread, I must say that conversely this sort of final opinion is also for me the consequences of "imposition of policy" unilaterally by like-minded thinkers.

     So in the end, I find these arguments hard to accept as criticism.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:40:29 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito Nothing is preventing me from hacking out behaviors I don't want except time and mental energy.

     The whole point was just drawing out that there is this big clash of philosophies underpinning these issues that's rarely examined.

   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:40:30 JST Raito Bezarius

     in reply to

     @dalias Still have difficulties to grasp. I can actually disable all dbus activation if I want on my system. Or have mathematical guarantees on such stuff. What is preventing your system integration to do so?

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:40:32 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito I don't want processes running as root to magically appear and become attack surface because some application I was running prodded a dbus address and dbus activation ran a daemon that happened to get installed as part of some package something else depended on.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:41:21 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito They're absolutely not of the form A|B. A|B is user-invoked or invoked by some script or controlling process that's neither A nor B.

     A-does-popen(B) is the analog of the dbus shenanigans.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:41:22 JST Raito Bezarius

     in reply to

     @dalias Yes, as it is that portals over D-Bus are kind of "A|B" in my opinion and distro shell scripts to make useful things out of non-systemd init looks like the popen coupling sometimes, but that's my opinion.

     Maybe that non coupling design is not coupling, but it can become in integration because of the lack of various things. Conversely, the tightly coupling dbus is just a bus and you could reproduce A|B with APIs, no?

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:41:23 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito If you want an analogy with pipes, program A invoking popen("B",...) would be a very primitive form of the sort of coupling I'm talking about, but largely unobjectionable if B is just processing data and not controlling some persistent state.

     The user invoking A|B is not a form this type of coupling.

     But none of this is an argument about doing things with pipes. It's about whether programs are aware of each other & addressing each other with IPC/RPC.

   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:41:26 JST Raito Bezarius

     in reply to

     @dalias I feel like this is a difference in wording, no? Or framing?

     Are you saying that two programs interacting via a pipe is a forbidden construction? Or is it an argument about how everything should enable you to control what you put in-between the pipes?

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 06-Mar-2024 23:41:27 JST Rich Felker

     in reply to

     • Raito Bezarius

     @raito You don't see how software avoids talking to each other. I don't see how it ever has a good reason to talk to each other in the first place. This is the difference in philosophy I was talking about.

   • Embed this notice
     Raito Bezarius (raito@nixos.paris)'s status on Wednesday, 06-Mar-2024 23:41:29 JST Raito Bezarius

     in reply to

     @dalias I honestly cannot comprehend, this seems to have nothing to do with the tightly coupling that we are talking about? I don't see how two software avoids talking to each other if they have to. Are you thinking of having the kernel or other primitive intervening here? If you want predictability, it's probably necessary to frame it in terms of static or dynamic description of the system, no?

   • Embed this notice
     [object Object] (zzt@mas.to)'s status on Wednesday, 06-Mar-2024 23:43:16 JST [object Object]

     in reply to

     • R. L. Dane :debian: :openbsd:
     • Irenes (many)

     @RL_Dane @dalias @irenes this is at the root of my distaste for systemd and the gnome ecosystem too, and it cuts deeper than any technical issues I have with systemd (though extreme resistance to technical improvements from outsiders does go hand in hand with cathedral-style development)

   • Embed this notice
     [object Object] (zzt@mas.to)'s status on Wednesday, 06-Mar-2024 23:43:16 JST [object Object]

     in reply to

     • R. L. Dane :debian: :openbsd:
     • Irenes (many)

     @RL_Dane @dalias @irenes also, it’s weird and fucking ridiculous that I have to maintain a large multi-service blocklist of systemd stans and red hat employees just to avoid being signal jammed with toxic nonsense every time I want to discuss anything negative about their ecosystem. this particular cathedral has already used its position to destroy our ability to effectively communicate, and I do resent that

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     R. L. Dane :debian: :openbsd: (rl_dane@fosstodon.org)'s status on Wednesday, 06-Mar-2024 23:43:17 JST R. L. Dane :debian: :openbsd:

     in reply to

     • Irenes (many)

     @dalias @irenes

     Really feels like the bazaar is turning into a handful of cathedrals.
     Gnome, systemd, and a couple of powerful distros laying down the law.

     Its creepy. And I actually *like* a couple (but not all) systemd modules.

   • Embed this notice
     Irenes (many) (irenes@mastodon.social)'s status on Wednesday, 06-Mar-2024 23:44:12 JST Irenes (many)

     in reply to

     • R. L. Dane :debian: :openbsd:
     • [object Object]

     @zzt @RL_Dane @dalias yeah... with Gnome, like, we don't use the desktop environment because it's just way too tightly integrated for our taste, but we do have some sympathy because a lot of what it takes to offer a pleasant UX is a unified design language that cuts across contexts

   • Embed this notice
     R. L. Dane :debian: :openbsd: (rl_dane@fosstodon.org)'s status on Wednesday, 06-Mar-2024 23:44:12 JST R. L. Dane :debian: :openbsd:

     in reply to

     • Irenes (many)
     • [object Object]

     @irenes @zzt @dalias

     I think the distaste with projects like that is that it's a small group trying to impose their will (in often petty* ways) over all.

     I don't get that feeling with the BSDs, even though it's literally one small group making nearly *every* decision about what goes into the OS.

     *Gnome apps looking like gnome apps in all DEs and breaking my OS/DE/personal theming and USABILITY is petty AF. I don't care about your glorious vision, people, sit the heck down.

     Haelwenn /элвэн/ :triskell: likes this.