modern programming is like,

"if you're using bongo.rs to parse http headers, you will need to also install bepis to get buffered read support. but please note that bepis switched to using sasquatch for parallel tokenization as of version 0.0.67, so you will need the bongo-sasquatch extension crate as well."

old-time programming is like,

"i made a typo in this function in 1993. theo de raadt got so angry he punched a wall when he saw it. for ABI compatibility reasons, we shan't fix the typo."

@saddestrobots Meanwhile, the build systems that they use.
@saddestrobots @scottmichaud my solutions to search stuff are:
find | grep bla
find | xargs grep bla
It doesn’t work of BSD and OS X. I try it at least five times a day as I use a Mac everyday. Sure I accept it was made to work this way, but really, would it hurt to allow me to type two characters less?
@chexum @saddestrobots @scottmichaud gave up on maintaining compatibility for scripts and started using #guile as an overall replacement

@morenonatural @chexum @saddestrobots I usually end up writing a python script or an executable and just running those on the command line.

One time I was asked to parse JSON in a bash script. They recommended that I used sed. I normally do as asked, but that time I just wrote a Python script because all the build servers had it. They accepted it, though. They apparently never thought of it.