this post was submitted on 22 Apr 2024
516 points (97.3% liked)

linuxmemes

21025 readers
821 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] [email protected] 1 points 5 months ago (1 children)

    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

    [โ€“] [email protected] 3 points 5 months ago

    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.