Live data from Hacker News

Systemd Linger

etbe.coker.com.au

31–40 of 96 posts

Re: Systemd Linger

#31

Systemd is simply too complex.

Which part? Just saying systemd is like saying a distribution is too complex

As a user I can say that journald was a mistake, if you try to reinvent a database, you will reinvent it poorly and journald wasn't an exception.

Re: Systemd Linger

#33
post #2

This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.

> Things not working the way I expect means I have to do more work to figure something out. Sound like you don't like computers to begin with

He probably just doesn't like having to use poorly written software

Re: Systemd Linger

#34
post #2

This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.

"The way you expect" is probably inconsistent and, upon closer inspection, completely broken. There is a reason why systemd became the default and other niche init systems have faded into obscurity. Sure, it may be more complex than your pile of shell scripts, but that's because it does the same things better, and has a lot more functionality that you will need at some point, and good luck replicating that by hacking…

> There is a reason why systemd became the default and other niche init systems have faded into obscurity.

Yes, it is part of the Embrace, Extend, Extinguish strategy

Re: Systemd Linger

#35
post #17
post #2

This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.

> This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out. Even if the change is a genuine improvement?

How can the change be a genuine improvement, if it does something unexpected that needs to be figured out?

Re: Systemd Linger

#37
post #2

This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.

In my experience, systemd is much better documented, way more consistent, and way more reliable than what came before.

Well, in my experience, systemd has much worse documentation, is very inconsistent (or you could say it is constistantly brain-dead), and extremely unreliable and unpredictable, since it often hangs when shutting down and rebooting.

Re: Systemd Linger

#38
post #5

Earlier quoted context omitted.

In my experience, systemd is much better documented, way more consistent, and way more reliable than what came before.

I guess it depends on your source of info but I've found what came before was pretty comprehensively & accessibly documented, at least as well as systemd, which - while well documented - suffers from sprawl & overwhelm of the docs. There's just SO MUCH to grok in comparison.

No way. I was easily able to create Systemd units from 0-knowledge, where the init system remains a big black box riddled with question marks for a very long time. Very little was documented.

Re: Systemd Linger

#39

Earlier quoted context omitted.

> Things not working the way I expect means I have to do more work to figure something out. Sound like you don't like computers to begin with

He probably just doesn't like having to use poorly written software

That's pretty much all software.

Re: Systemd Linger

#40

Earlier quoted context omitted.

In my experience, systemd is much better documented, way more consistent, and way more reliable than what came before.

Well, in my experience, systemd has much worse documentation, is very inconsistent (or you could say it is constistantly brain-dead), and extremely unreliable and unpredictable, since it often hangs when shutting down and rebooting.

systemd is like the registry. If you drink the koolaid and fully admit and adopt the decisions made, you’ll do ok, perhaps even good.

If you have 20+ years of experience, you’ll will NEVER get it to work the way you expect, might as well install Gentoo.

Post reply on HN