Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Bad idea.
Mind elaborating?
Not OP, so i've got no idea why they think it's bad, but systemd breaks with unix's key design principles, and monopolizes and absteacts more and more aspects of system management. Some people do not like this.
A while ago I read through the classic Unix Programming Environment from 1984 while trying out the things described on a Debian system. I like the unix philosophy. Ken is a genius. ed is the standard editor. The more I read though, the more I was thinking that this just isn't how we use computers today. I think Linux is trying to be two things at once. On the one hand it's sort of a UNIX-clone, on the other hand it's a black box that our containers and browsers and applications rest on. I'm not sure why we are heading towards less and less UNIX, but it seems to be by popular demand?
IMHO, you cannot apply the UNIX philosophy to a GUI.