Earlier quoted context omitted.
I feel likewise (except for the Perl part. I have the most fun working with PLT-Racket tools). I believe this happens because language design involves a lot of trade-offs, so every language incorporates these trade-offs. When one is comfortable in many kinds of languages, one is in a special position to see the trade-offs in the design of the language one is currently programming it. The way I see it is slightly diff…
Tradeoffs are a sign of a false dilemma; rather than choosing one solution or another, use them all where they work best. This is where Unix got it right all those years ago; Unix isn't just a slightly more stable platform for running today's bloated and monolithic software, rather, it's an elegant system for connecting maintainably-small utilities. The shell glues said utilities together into programs. Such an appro…
And I think it is no coincidence that the creator of Unix is one of the designers of Go, a language that shares Unix's conceptual and implementation simplicity, makes very conscious tradeoffs and where channels work somewhat akin to pipes.
Of course interfacing with the rest of the world has become much harder thanks to XML, SOAP, XMPP and every other such monster, but as somebody else pointed out, the modern equivalent seems to be REST+JSON, I would have preferred something like 9P, but oh well, one has to pick their battles.