5 ms·

Your terms are impossible to meet. The moment I reach one goal, you'll invent another. Not worth it my dude. I am doing something about it by researching ways

Your terms are impossible to meet. The moment I reach one goal, you'll invent another. Not worth it my dude. I am doing something about it by researching ways to excise Red Hat from as much of the tech stack as possible. Can't do much about the kernel, but every layer above it is moldable. I don't care to provide 'usefulness' to you; if you're not paying me why would I give up any value? It was an arrogantly managed project using the guise of standardization to bypass people's social tendencies. People are stupid, so they fell for the 'only consider the code, not our social fuckery!' Hook, link, and sinker. It really opened my eyes to how ignorant and passive a lot of techies actually are. They're happy to slurp up whatever's advertised to them as the better thing. Systemd runs my current laptop and I hate having to dive under the hood for anything. In a sysvinit, runit, or OpenRC system, I can achieve things quickly and don't need a book's worth of corporate style documentation to operate my damn system. Systemd still doesn't support a one-time script on boot. You have to hack together a unit for that. Most other systems just run an rc.local script in /etc! Binary logs are only useful if systemd is running, and only that version of it too! Good luck understanding journalctl output. It doesn't capture everything. Long story short, systemd has not improved a single area of my computing life. I guess I can ogle at a boot time graph. But the main goal seems to be for systemd to take away knowledge of the lower levels of the stack. Like it or not, open software ecosystems are resistant to standardization by default. Systemd and dbus and friends would not have bothered me if they weren't coupled with weird ideology about One True Linux or other crap. Systemd never solved problems for me. I'm sure it solves many business problems but none of them apply to me.

Novosell 3y ago
You think systemd was developed as a ploy to make people more ignorant? With what goal in mind? Selling support contracts?
- zlg_codes 3y ago
  I think systemd was developed to make a libre replacement for SMF, that supported socket-based activation and deterministic boot. Those were two of the project's original goals, but the endgoal I think was to develop this capability for open source Red Hat, SuSE and friends, get it on every distro, then use their influence at lower levels of the stack -- only one higher than the kernel itself! -- to have effective control over the open source ecosystem at a low level. Poettering worked for Red Hat during the development of both PulseAudio and systemd. If he was not writing code they wanted, he would have worked on another project. Ergo, one can conclude those projects to be Red Hat-oriented, or sponsored at minimum. I firmly believe the profit motive in the software world is what leads to dark patterns, user-hostile design, and other maladies we face in the modern software world. Their obligation to seek profit over all other things leads to compromised values, leading to compromised software.

Novosell 3y ago

You think systemd was developed as a ploy to make people more ignorant? With what goal in mind? Selling support contracts?

zlg_codes 3y ago
I think systemd was developed to make a libre replacement for SMF, that supported socket-based activation and deterministic boot. Those were two of the project's original goals, but the endgoal I think was to develop this capability for open source Red Hat, SuSE and friends, get it on every distro, then use their influence at lower levels of the stack -- only one higher than the kernel itself! -- to have effective control over the open source ecosystem at a low level. Poettering worked for Red Hat during the development of both PulseAudio and systemd. If he was not writing code they wanted, he would have worked on another project. Ergo, one can conclude those projects to be Red Hat-oriented, or sponsored at minimum. I firmly believe the profit motive in the software world is what leads to dark patterns, user-hostile design, and other maladies we face in the modern software world. Their obligation to seek profit over all other things leads to compromised values, leading to compromised software.