For what it's worth, this has recently become a 'standard' interview question for developers. I predict that people will start game it by having a canned response, thereby rendering it virtually useless---just like all other standard interview questions.
I used to ask interviewees to discuss what they didn't like about their favorite language. If they had a hard time finding stuff to criticize, there was a good chance they didn't really know the language. or were not particularly critical developers.
Which is fine if, when pressed, they can back up what they say. The question (like most good interview questions) is largely an excuse to help guide a conversation and some exploration to avoid canned responses.
Granted it's still a terrific question -- expository about the applicant, and easy to banter about to detect bullshit / plagiarism.
Argh. I hate catching typos in my own comments.
"You're in the desert, you see a tortoise lying on its back, struggling, and you're not helping -- why is that?"
'Do you make up these questions? Or do they write 'em down for you?' ~ http://www.imdb.com/title/tt0083658/quotes
You must be able to criticize what you love to be a good programmer.
Yes, it would bait idiots who "don't like C because you can only define variables at the top of a function", or "don't like Java because you have to put classes in different files" -- but that's intentional.
As in 11 not-real languages. Languages that don't exist?
I'm not sure I follow.
I never end up using Perl, the niche it occupies between shell and python is empty for me. I never have a problem with a shell script where I'm wishing for more control structures or builtins. The few times I've written long-running resource-intensive shell scripts (like brute-forcing an MBR partition scheme), reducing the number of forks wouldn't make them more than a few percent faster.
The major ray of light shining down on Ruby is that it is a Perl that people want strongly to write better looking code in. That's a pretty big accomplishment, I think. It seems like a lot of the classic Perl webdev shops are moving to Ruby, and I think that's pretty great.
I don't hate Ruby, I'm just disappointed in it.