Published Nov 19, 2026, 9:00 AM EST Simon is a Computer Science BSc graduate who has been writing about technology since 2014, and using Windows machines since 3.1. After working for an indie game studio and acting as the family's go-to technician for all computer issues, he found his passion for writing and decided to use his skill set to write about all things tech. Since beginning his writing career, he has written for many different publications such as WorldStart, Listverse, and MakeTechEasier. However, after finding his home at MakeUseOf in February 2019, he would eventually move on to its sister site, XDA, to bring the latest and greatest in Windows, Linux, and DIY electronics. One of the coolest parts of computing is discovering that the tech you're interacting with on a daily basis was invented decades before your PC even existed. One of them kicks in whenever you use the terminal, and while you don't see them working away in the background, you can invoke them at any time. It's the humble pipe, and its invention starts with a note all the way back in the 60s. The pipe began with the desire to make a digital garden hose The final name didn't deviate too far from the idea of liquid transit In 1964, Douglas McIlroy (the visionary department head for Bell Labs) had a problem. Back then, programs were pretty monolithic; they didn't come with the ability to naturally share data between two programs. Instead, you had to manually write code that would translate data from Program A to Program B. If you wanted to perform a sequence of actions, that would involve a lot of work chaining together these individual tools to get the job done. It was rough work. On October 11, 1964, Doug McIlroy had had enough. In a memo titled "What's most important," he had an idea as to how things could be better: “We should have some ways of coupling programs like garden hose – screw in another segment when it becomes necessary to massage data in another way. This is the way of IO also.” The good news is, McIlroy was on the money; such a system would make it a lot easier to perform tasks that are linked together. The bad news is, Doug McIlroy had to pester Ken Thompson, a Unix co-creator who joined in 1966, for years until he finally caved and added the pipe() system call in February 1973 after a night of coding. They were pretty much a hit from day one. McIlroy recalls what the first day with pipes looked like at Bell Labs, stunned that all the chaining together they had been doing for years could now be achieved with a single line. Because pipes could pass out data via their stdout data channel and take in data using the stdin channel, you could daisy-chain them and have data flow through each command, much like a hose. The very next month, in March 1973, McIlroy asked Thompson to "lift the regular expression recognizer out of [an] editor" and turn it into a program he could invoke anywhere. The next day, Thompson created global regular expression print, or 'grep' for short; a command we still use today! The new, fancy pipe technology showed up the old ways The moment when a dinosaur was shown for what it is The elegance of pipes would be put into the spotlight in 1986, when Jon Bentley, who owned a column called "Programming Pearls" in the publication "Communications of the ACM," asked programmer Donald Knuth to write a program that would take in text, count the most frequently used words, then rank them in order alongside their occurrences. Knuth got to work, and when he came back, he had over ten pages of Pascal code to get the job done. His code was passed over to McIlroy for critique, who praised Knuth's program and said it was very clever, despite having a few bugs. He then proceeded to completely obliterate Knuth's program with the following proposal: tr -cs A-Za-z '\n' | tr A-Z a-z | sort | uniq -c | sort -rn | sed ${1}q Using pipes, he could split words onto separate lines, lowercase everything, sort them alphabetically, count all the duplicates, sort them by frequency, and grab the top few entries of the list. It fits on a Post-It Note, and it became a famous example of how pipes helped people do more, quicker, with less effort. The pipes still put in work today The plumbing still works So, where are those pipes now? Well, they're still being used daily, and there's a good chance you'll use them at least once in your life if you use Linux—much more so if your job or hobby requires lots of terminal commands. For instance, if a Linux user wanted to find the process ID for nginx, they'd open the terminal and type: ps aux | grep nginx The "ps aux" part grabs every running process, and "grep nginx" finds lines containing "nginx" in the output. The pipe connecting the two together allows "ps aux" to hand over the text via stdout so that grep can grab it using stdin and find the target word. All you need is four words and a pipe, and you're golden. Chaining commands together went from pipe dream to pipe-based reality The next time you're typing a command into your Linux terminal and you find yourself reaching for the trusty pipe, give a thought for the decades of engineering that went into it. It's a lot easier to write than ten pages of Pascal, that's for sure.
Unix pipes are over 50 years old, and they're still why the Linux terminal feels so powerful
Full Article
Original Source
Read the full article at Xda-developers →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.