This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.
Either way the whole point is to write programs/code that can interoperate and be composed. SysD programs comunicate over an “implementation is the specification” protocol, so they might as well be one blob instead of separate programs.
What’s the Unix philosophy?
catb is full of great info, including the answer to the question.
http://www.catb.org/~esr/writings/taoup/html/ch01s06.html
Edit: replaced with the succinct version.
Ooohhh, I’ve been reading bits of catb.org since I was like 13!
Using one specific source for the definition of the Unix Philosophy is against the Unix Philosophy. /s
Everything does 1 thing, programs work together
I think Linux just doing the kernel should count as Unix philosophy though
Originally it was about code. Split it into reusable functions, and such.
SyStEMd fans don’t understand, per usual.
Where did I defend systemD?
Reply was to you, but it’s still a public forum with a topic.
Is it not about chaining processes?
IIRC the ideia was to use pipe (or other methods) to send one program’s output to another’s input
But it very well could be about reusable functions, as code or as a .so file
Hmm. I can’t find ehere i got that from, other then it being more general. https://cscie26.dce.harvard.edu/lectures/lect02/6_Extras/ch01s06.html
Either way the whole point is to write programs/code that can interoperate and be composed. SysD programs comunicate over an “implementation is the specification” protocol, so they might as well be one blob instead of separate programs.
I see. I read the catb page and I think it’s a good direction.
“Do one thing but do it good” and "everything is a file. Is there more?
Probably the opposite of what “GNU’s Not Unix” does.