unix_philosophy

created: 2023-04-11T18:59 Tue
tags: unix philosophy public

Make each program do one thing well. To do a new job, build afresh rather than
complicate old programs by adding new "features".

Expect the output of every program to become the input to another, as yet unknown, program. Don't clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don't insist on interactive input.

Design and build software, even operating systems, to be tried early, ideally within weeks. Don't hesitate to throw away the clumsy parts and rebuild them.

Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you've finished using them.

Remember - to do a task, it is best to build a tool for it if you have to do it more than once. https://www.youtube.com/watch?v=ttWimGhXwHU

https://tools.suckless.org/quark/
^^ this site in general seems to be a good resource.

http://harmful.cat-v.org/software/

[[unix_house]]

https://github.com/httpie/cli
to try: xplr, httpie