This immovable status quo also means that you will encounter a hodgepodge of languages ... most commonly these days, the three you mentioned plus PHP and JavaScript ... in any existing project that you might encounter in the field.   Since rewriting is simply “starting over,” and refactoring is almost a euphemism for the same thing, you are quite stuck with needing to know multiple languages without picking favorites.   Whatever dress the grand dame wore to the ball, is the same one she will leave in.

You can try valiantly to introduce a new language into an existing system or “shop,” but the end result is simply that you’ve added yet-another one.   And, a very critical issue is raised thereby which is often overlooked:   libraries.   Unless the libraries in two different languages merely “wrap” the same .so or .DLL, they probably are not exactly identical in their implementation therefore behavior.   Two parts of the “same” system are actually apples vs. oranges, and the surprise-deficiencies of a library in one language vs. another can wreck a project, even when the custom-source that has been written is genuinely(!) “–er.”   Another compelling reason to stick with the beaux that you know, even if it occasionally requires liquor or deodorant.   (With regards to it, and/or with regards to you ...)   ;-)

And the situation on mobile devices is much worse, because the market is split between several aggressively-competing vendors, each with their own proprietary platform, each based on different languages.   “Cross-compiler” solutions aren’t standardized, some are ill-funded, and then there are the folks who simply want to turn a mobile device into Flash or a thinly-disguised HTML website.   This dissipation of focus and therefore effort will never end.

So, go ahead ... have your preferences.   (Perl’s a great language to prefer.)   But meanwhile, learn as many programming tools as you can, because you will need them all.