News for hackers. Stuff that matters.
Re:The Tragedy of Systemd [video] by loeg on Wednesday February 20, 2019 @02:06PM (#19210924)
> The benefit is that it's logged, always, and through a mechanism that is the same for every process. It's a trade off. We can argue whether it's a worthwhile trade off, or one that even really needs to exist (is there a reason they don't immediately show an error? I don't know)

Yeah, it seems feasible (and maybe a good default) for systemctl to dump out the same last few lines it would for 'status' if an administrative request fails. I don't know why this has to be a tradeoff; systemctl actions could easily both log and print (some limited subset of) the log on error.

Re:The Tragedy of Systemd [video] by isostatic on Wednesday February 20, 2019 @02:39PM (#19211235)
Logging it is great, it's the fact the interface says "look in the log" rather than doing it for you.

It's tiny annoying things like that which leave a bad first impression. Rather than going "hey this system is great, it logs what it tells me", instead I'm left thinking "this system isn't for people like me, it doesn't think I need to know why it's broken"

First impressions are so important.