zlacker

>>InitEn+(OP)
I am a fan of this concept, I've thought a lot about it actually. Having a proper open source option is awesome and there is no doubt I'll be trying this on some of my home/hobby infra to see what it has to offer. If nothing else, I really think we need more exploration into the space of adding some basic engineering and ops on top of things like this.

Not just for servers and infrastructure, but does it bother anyone else that for example, the Linux desktop has robust APIs for managing powerful service daemons like systemd, but relatively few applications that use them and provide useful UIs/control panels/dashboards? Somehow for many of the tools we DO have, the Linux desktop is stuck in the age of using popen and regex against command output even though we really ought to be able to do better. It's an odd blindspot in a lot of open source work, maybe it is deceptively difficult!

That's mostly nothing to do with this project though, but the two problems are intertwined in my head as problems where a little bit of engineering could really go a long way.

>>jchw+xl
For your consideration. A single tool that does many jobs is in some ways contrary to linux/unix philosophy of creating tools that do a single job.

>>0r30+JV
I am not really asking for tools that do a lot of jobs, though. A simple program that manages systemd services or provides a nice UI around journald logs seems completely reasonable to me.

That said, I don't take the UNIX philosophy to be gospel, and frankly, very little of the Linux kernel or desktop really seems to. That seems to be closer to what the *BSD derivatives would steer towards. I just want a functional operating system, and the specific ideology or design of packages isn't too big of a concern so as long as the end result seems solid.