Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 08-Mar-2024 09:19:19 JST Haelwenn /элвэн/ :triskell:

   • Enno T. Boland
   • Chimera Linux
   @ariadne @chimera_linux @Gottox That's probably the case but what happened from outside is systemd being shoved because software essentially from Fedora/RedHat (such as gnome projet and related aka the main/reference desktop environment and toolkit) depended on it hard enough to need custom patches that wouldn't be merged upstream.
   
   It definitely wasn't grassroot as in major distros reaching a consensus, and I don't think most can do that much distinction between redhat and fedora without being implied in one or the other.
   (Corporate conspiracy being speculation from there, and of course bullshit but that's politics for you)
   • Embed this notice
     Chimera Linux (chimera_linux@floss.social)'s status on Friday, 08-Mar-2024 09:40:48 JST Chimera Linux

     in reply to

     • Enno T. Boland

     @lanodan @Gottox @ariadne even if that was the case it's not right to blame gnome here; their lives would be much easier with just systemd as right now there are two process launch architectures simultaneously maintained (desktops consist of a lot of session-wide processes, and gnome can now either launch them with systemd which means being able to do so cleanly, on-demand, in a supervised manner and with dependencies, or in a crummy "just launch everything and hope it does not crash" way)

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 08-Mar-2024 09:47:13 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Enno T. Boland
     • Chimera Linux
     @chimera_linux @Gottox @ariadne Yeah, I can understand why gnome did it (after all a desktop has a lot of services either system or user) and they're one example among many others, I'd also say the lack of understanding of gnome needs.
     
     The annoying part is it looks like it happened in a rather unilateral way with direct dependency on systemd (specially libsystemd) rather than "we need services to be managed, we found systemd to be elegant for this, but you can choose something else which does the same thing".
   • Embed this notice
     Chimera Linux (chimera_linux@floss.social)'s status on Friday, 08-Mar-2024 09:47:14 JST Chimera Linux

     in reply to

     • Enno T. Boland

     @lanodan @Gottox @ariadne the latter is the "traditional" way and it was bound to happen that as soon as there was something better somebody would jump on it

     unfortunately we still have to live with the latter (gnome is nice enough that they still maintain vast majority of the old paths even though they have no obligation to) though in a few months we'll be ready to switch to a better architecture

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 08-Mar-2024 17:59:28 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Enno T. Boland
     • Chimera Linux
     @chimera_linux @Gottox @ariadne Yeah, that said imagine if wayland applications would explicitly link to libweston instead of well… having a specified protocol called wayland with just an optional support lib.
     (Or take any other freedesktop standard but hardcode to a major implementation)
   • Embed this notice
     Chimera Linux (chimera_linux@floss.social)'s status on Friday, 08-Mar-2024 17:59:30 JST Chimera Linux

     in reply to

     • Enno T. Boland

     @lanodan @Gottox @ariadne what something else? there *wasn't* anything else they could have realistically used at the time (to a degree there still isn't)