in reply to Perl and the Future
My personal take on the “popularity,” or perceived lack-thereof, of the Perl language ... is that it is irrelevant. There is always a new language coming along, and new projects might be started in one of those. But the vast majority of software that is in-service is so-called “legacy” software ... existing software, mission-critical, and by the way “it works just fine, thankye.” Therefore, one of the most important “life skills” for any professional programmer, in my opinion, is adaptability. To quickly learn how a system was written and how to maintain that system without attempting to rewrite it. You could say exactly the same thing, for exactly the same reasons, about any legacy system that was written in Python, Ruby, or Lua.
<<language_x>> does not need to be popular with the up-and-coming generations in order to be relevant, and most of the languages they’re advocating right now will in due course become “cool” if measured by the same yardstick. (They just don’t know it yet.)
. . .
Aside: And as for “what’s about to become very significant, especially in the apps/mobile world, I will cordially suggest that something’s on-the-scene now that will ... along with other tools in the same vein ... sweep both web-development and app-development off its feet, by introducing the notion of compiling one strongly-typed(!) source language to multiple native targets. That revolutionary language is called Haxe, along with OpenFL which is built on top of it. You won’t be writing directly in JavaScript anymore, nor will you be running around on “HTML5 website-in-an-icon crutches” when you want to deploy a mobile app, or wondering if device-X has enough market potential for you to “start over from scratch” writing “your app” for it. That toolset hasn’t yet hit the main stream, but it is illustrative of just what kinds of changes can occur. These are not “yet another way of doing the same thing in the same way,” but a fundamental and disruptive change in the way that things are done which meaningfully addresses the costs of doing it.
Replies are listed 'Best First'. | |
---|---|
Re^2: Perl and the Future
by mr_mischief (Monsignor) on Mar 30, 2015 at 19:15 UTC | |
Re^2: Perl and the Future
by kmadhyan (Initiate) on Mar 31, 2015 at 08:31 UTC | |
by Anonymous Monk on Mar 31, 2015 at 08:45 UTC | |
by einhverfr (Friar) on Apr 16, 2015 at 12:14 UTC |