Amikke @Amikke@qoto.org

@Luap314 @lemba @nixCraft alright, I went overboard with that one, I forgot that there's sadly a deplorably big group of well-meaning green organisations that oppose it due to plain ignorance and fear, and the pro-nuclear green movement is only a sub-group, even if big, growing and scientifically supported.

Events like entire green organisations or their parts being funded by oil magnates, and high-ranking politicians behind Energiewende being allegedly bribed with Gazprom positions for making Germany shut down its nuclear plants in favour of Russian gas and the promise that it's only temporary and they're totally gonna replace all of it with renewables any day now certainly don't help.

@BrodieOnLinux apparently not every. TIL tho. Both approaches have their advantages.

@BrodieOnLinux isn't that what everything does? It's a workspace, not a monitor instance.

@lemba @nixCraft you mean glad, right? Sorry, can't read the article due to their donate button taking 1/4th of my phone's screen, but pretty much all actually green organisations are proponents of nuclear due to its lowest impact on the environment and those that oppose it are usually the Germany case - literally paid off or even funded by oil industry giants.

@lemba @nixCraft you mean the 5 grams or so it will directly produce over its lifetime? I think we'll survive. Quick reminder that nuclear power plants produce less nuclear waste per megawatt than coal power plants, and take better care of it. Also, 0 CO2.

@icedquinn oh yeah, udev functionality is cool too, from what I see runit only sets up things once and doesn't respond to changes. So I'd have to install something that does that. I assume there's a lot of other "bloated" systemd functionality that is quite useful and installing separate tools to do all of them so that they don't have to be coupled with the pid 1 would exceed the bug surface.

@Palleas @b0rk that's why the "usually" clause is there I assume

@icedquinn I think I count as people and I expect PID 1 to not just start stuff but also monitor it and make it available under a consistent API and consistent logs, so that I can use it to control the system instead of babysitting every single daemon their own way.

From what I can tell trying to muh unix philosophy to split it into different services that still do those things instead of falling back into bad ol' anarchy would just require a few different services that have the same basically infinite permissions and accomplish the same thing but with more bloat, attack surface and weird shit.

I guess if you prefer the anarchy disliking it makes sense tho.

@icedquinn if this level of unfathomably based requires systemd I'll happily accept systemd. Besides, I still haven't heard sensible arguments against it, only variations of "but it enforces a sensible API", "but it uses 5M of memory, that's way too much" or "but there's a bunch of related tools you can optionally also install so systemd itself is bloated "

@icedquinn nixos itself is the better gentoo tbh

@icedquinn skype probably deserved to be called a finely crafted desktop program those 15 years ago when it wasn't yet bought by the likes of MS and enshittified, and didn't yet have sensible competition. From what I remember about using it like 8 years ago it was already buggy and very annoying back then.

@BrodieOnLinux having it build for 4 hours just to restore those parts of the config and have it rebuild for another 4 hours was the cherry on top, great system.

@BrodieOnLinux my favourite moment when installing Gentoo for the first time was when I carefully configured the USE flags to fit what I want, got thrown into the deepest circles of dependency hell and after painstakingly trying to solve it learned that you first have to build it without USE flags and only then configure it because apparently after all those decades Portage is still too stupid to resolve dependency issues like "package A needs package B only due to a USE flag and vice versa gee I wonder how I could solve that problem".