The successor to Perl is Ruby. System administration used to mean Perl, now it means Ruby. Fast web development used to mean Perl, now it means Ruby or Python. The successor to Perl is Ruby.
Yeah, I'm gonna have to completely disagree with you here.
I'm a sysadmin that does a decent amount of automation and scripting work. Almost all of that is done in Perl. Among the other guys on my team, everyone uses Perl, except for one person who uses Python.
We had one person who came into the team as a Ruby fan. Within 6 months of working with us, she'd become a Perl fan. She told me she'd passed on Perl and gone to Ruby because she'd heard bad things about Perl. After seeing it in use and checking it out a little closer, she realized that almost everything she'd heard "bad" was outdated, incorrect, or overstated.
Outside of my team, I know lots of people who use Perl, a decent number of people who use Python, and a very small number of people who actually use Ruby. Yeah, there's a few high-profile apps in it, and yeah, Ruby on Rails got it a lot of attention for quick and dirty web apps, but it has a long way to go before it'll reach anywhere near Perl (or even Python) is.
I'm not into the whole sys-admin thing or the Ruby hotness or the Node.JS hype but I noticed that there are more utilities or tools that are written in Ruby lately.
CloudFoundry seems to be written in Ruby and it looks like a bunch of sys-admin tools.
Chef, Puppet are both written in Ruby and utilized Ruby (or Ruby DSL?).
There's a strong push for Ruby lately and it might be because Ruby is kind of similar to Perl so some sys-admins are okay with that?
When ever I drop in to write sysadmin scripts, I choose ruby, python or powershell depending on the platform. I never choose bash/dos batch/perl anymore.
Granted I'm a developer who does sysadmin on the side.
Edit: (Python on ubuntu, Powershell on windows, ruby on everything else. Python on ubuntu since it's there out of the box)
When I start writing something, I think about how big I expect it to be. If it's expected to be 50 lines or less, then it's bash for general scripts, and awk for text filtering. If it's expected to be more than 50 lines, I go with Perl. That goes regardless of platform (as it's already available on every *nix platform I use, and Strawberry or ActiveState makes Perl easy to add on Windows).
I'm also a developer who still does sysadmin on the side (and probably far too much for my liking!) and I always write my scripts in Perl or bash.
And from what i've seen and anecdotally this still seems to be the common case (Java & Perl are the main languages used by companies in the City of London).
Actually nothing ever truly replaces those classic tools bash/awk/sed/perl.
But every now and then you will see <insert some new tool> being compared with a <insert classic tool>. And then told since the <insert some new tool> is a little famous now, its likely to replace the <insert classic tool> and that <quote some irrelevant search engine statistic> actually proves <insert classic tool> is dead and <insert some new tool> is actually going to replace the <insert classic tool> in the future.
Then suddenly expect a stream of tweets, blog posts and forum discussions on how useless <insert classic tool is>.
Please replace <insert classic tool> by "Perl","SQL","Php".
Please replace <insert some new tool> by "Python","Ruby","Tcl","NoSQL","Django"..
Please replace <quote some irrelevant search engine statistic> by Google search stats or Tiobe(Which is the same ,but presented differently metric).
Sometimes a new tool will come along that truly is a huge improvement on previous tools. But, when those previous tools are "classics", it's pretty rare that the "new" tool is truly that much of an improvement.
There's a reason that these things (bash, sed, awk, perl, SQL, Unix/Linux, etc) are still popular and still going. It's because they're time tested, they're well known, and they work.
While it's good to always review your tools & skills... spending lots of time looking at sparkling new things could be better focused on i) getting work done or ii) improving your proficiency with current tools :)
