@[email protected] to [email protected]English • 2 months agoHow to pickup girls 101sh.itjust.worksimagemessage-square48fedilinkarrow-up1531arrow-down114
arrow-up1517arrow-down1imageHow to pickup girls 101sh.itjust.works@[email protected] to [email protected]English • 2 months agomessage-square48fedilink
minus-square@[email protected]linkfedilink8•edit-22 months agoEverything does 1 thing, programs work together I think Linux just doing the kernel should count as Unix philosophy though
minus-square@genslink3•2 months agoOriginally it was about code. Split it into reusable functions, and such. SyStEMd fans don’t understand, per usual.
minus-square@owseilink1•2 months agoIs 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
minus-square@genslink3•2 months agoHmm. 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.
minus-square@[email protected]linkfedilink1•2 months agoI see. I read the catb page and I think it’s a good direction.
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.
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.
Where did I defend systemD?
Reply was to you, but it’s still a public forum with a topic.
I see. I read the catb page and I think it’s a good direction.