I have to disagree. It's true that Perl is not the only language that saves people time, and it's true that many of the things people mention in threads like this could have been done equally well in Python, say. But it's not true that anything Turing-complete is equally good at time-saving.

In my case, when I say "Perl saved me time", I typically mean "CPAN saved me time". The extraordinary depth and variety of libraries available at the touch of a button does make a real difference in my work, and does save me a significant amount of effort relative to working in some other languages, such as C++.

Even for languages with rich libraries, the learning curve for those libraries may differ wildly. Just recently I needed to produce a simple GUI application in a hurry. I wasn't familiar with any of the options. I actually gave some serious thought to using Java, since that would have had certain advantages in this instance. But I took a long hard look at Swing, and then I took a short hard look at Perl/Tk,* and it was quite simply a good order of magnitude simpler. It would have taken me several days to get anything working in Java, while with Perl/Tk I had a functional prototype by the end of the afternoon.

(Could Tcl have saved me just as much time? I doubt it; I was using a number of other CPAN libraries in the same project. Did Perl itself have anything to do with the simplicity? Yes; it has proper closures with a lightweight syntax, which makes defining callbacks much simpler than Java's cumbersome anonymous-inner-class approach. Am I claiming it's better than Java for all purposes? Not at all. I would hesitate to deploy a Perl/Tk app enterprise-wide; Java's lack of expressiveness comes hand-in-hand with a much greater availability of maintenance programmers, and I have no end of respect for their remarkable ability to tolerate endless VerboseBoilerplateFactoryVisitors.)