0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 2 months agoHow to pickup girls 101sh.itjust.worksimagemessage-square48fedilinkarrow-up1530arrow-down115
arrow-up1515arrow-down1imageHow to pickup girls 101sh.itjust.works0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 2 months agomessage-square48fedilink
minus-squareowsei@programming.devlinkfedilinkarrow-up1·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-squaregens@programming.devlinkfedilinkarrow-up3·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.
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.