9 ms·
Why Perl Didn't Win
- winter_blue 12y agoAt the end of the article, he/she says "the Swift programming language has been public for less than a week and already has more users than Perl 6, and Swift is entirely built on technologies which have been invented since the Perl 6 announcement". That's simply false; anyone who's been in the programming languages field for a while knows that...
- aaronbrethorst 12y agoI interpreted that as 'Perl 6 dates back to 2000, while LLVM (upon which Swift is built) dates back to slightly later in the year in 2000.' (although, to be fair, the LLVM website first appeared in 2002.)
- steveklabnik 12y agoI have two programming tattoos: a Perl camel and a Ruby ruby. That basically tells the story of why Perl didn't win for me: As soon as I started learning Ruby, I thought, "Oh, a cleaned-up Perl" and never really wrote any Perl code again. I love Perl's personality, its quirkiness, and its massive amount of libraries. Perl was _massively_ influential on me as a young programmer. But I'm pretty sure that I won't be writing any Perl ever again.
- Roboprog 12y agoExactly. Perl 6 was forever delayed, and along came Ruby. Or rather, out from the shadows came Ruby, which was already there before the Perl 6 debacle, and just needed promotion. The Pragmatic Programmer books were pretty good at pointing to this cool replacement for Perl that you never knew was already there (as well as all the buzz from the RoR folks for those of us who weren't in on the beginning) I don't really think that the people who left perl all went to PHP. Now if only there was a "Ruby lite" that ran more like Perl 5 (skipping the GC for reference counting and a few other performance shortcuts)
- Poiesis 12y agoI'm wondering if Swift will fill that role, eventually.
- Roboprog 12y agoI hope so. That is, I hope there is a version of Swift outside of Apple-land (Clang compiler for LLVM extension???). What little bit I have seen so far looks promising, and it has a significant sponsor to get the language going.
- mst 12y agoruby is awesome until I want OO ... then I get about an hour in and find that I've got to write 5x as much boilerplate as I would under Moose/Moo, and there's no proper trait/role system, and then I get annoyed and go back to perl. If ruby had OO as good as Moose, I'd seriously consider switching. Sadly the projects to port Moose to ruby never seem to get finished.
- steveklabnik 12y agoMoose came out five or six years after I made the move, so I'm not super familiar. Can you expand on some of this? I very, very rarely need 'boilerplate' in Ruby...
- mst 12y agoTwo examples. Note that I'm going to write the boilerplate-ish version in perl as well, because I think it'll be equivalent and that's probably more likely than not screwing up the ruby code. Please correct me if it isn't equivalent. Most of my object attributes look like one of - has foo => (is => 'ro', required => 1); has bar => (is => 'lazy', builder => sub { Some::Logic::here() }); which translates through to, in old-school perl style, sub new { my ($class, $args) = @_; my $new = bless({}, $class); $new->_init($args); return $new; } sub _init { my ($new, $args) = @_; die "foo is required" unless exists $args->{foo}; $new->{foo} = $args->{foo}; if (exists $args->{bar}) { $new->{bar} = $args->{bar}; } } sub foo { $_[0]->{foo} } sub bar { my ($self) = @_; unless (exists $self->{bar}) { $self->{bar} = $self->_build_bar; } return $self->{bar} } sub _build_bar { Some::Logic::here(); } So far as I'm aware, ruby provides 'attr_reader' which would generate the 'foo' method for me, and of course the above 'new' is built-in. However, again so far as I'm aware, I'd still have to write the bar() lazy/build accessor, and an initialize() method to do the equivalent of '_init' - and name _build_bar by hand, which is less of a big deal but turns out to be really quite nice. Plus I'm unaware of any ruby equivalent for the Class::Method::Modifiers CPAN module, although I'd imagine that's pretty easy to write and wouldn't be surprised if there's a gem somewhere that I've missed. In fact, there's a MooseX gem that brings some of this syntax to ruby already, which suggests that it isn't already there anywhere else or at least that that gem's author didn't find it either; next time I play with ruby I intend to do so with the assistance of said gem and maybe that'll solve my problem, but I'm open to being told I'm doing it completely wrong - this isn't me harshing on ruby so much as complaining that an otherwise rather pretty language isn't something I can enjoy writing and I'd like to fix that.
- lovelyday 12y agoWrite once, read never.
- Roboprog 12y agoSpeak for yourself! (or maybe, for annoying coworkers???) It's certainly possible to write functions (subs) with comments about what they do, and use meaningful variable names. The built-in syntax/operators do require some study, though. For the "Enterprise!" developer pool, there's Java. The 500 line methods are still hard to slog through, though. Too many never got the note about a "business logic layer" and abstraction, and just shove all the details in-line. In which case, the language of mandate doesn't matter much.
- EdwardDiego 12y ago> For the "Enterprise!" developer pool, there's Java. The 500 line methods are still hard to slog through, though. Great straw-man there. I didn't realise that javac required 500 line methods before compilation. > In which case, the language of mandate doesn't matter much. It's a lot easier to pass two collections to a method in Java than to a sub in Perl.
- deleted 12y ago[deleted]
- EdwardDiego 12y agoYour reply makes no sense to me I'm afraid. > And I didn't realize the well written Perl code compiles equally better. Equally better? > And its certainly a lot easier to open files and do things in Perl than writing several hundreds of lines just to set and get variables for one single class. Come on, seriously. Here's how I open files in Java: import com.google.common.io.Files; List<String> lines = Files.readLines(new File("/foo"), Charset.UTF8); Why do you insist on straw-men to back up your arguments?
- deleted 12y ago
- jacques_chester 12y agoThe final section, which I was anticipating for the whole article, was essentially this: http://en.wikipedia.org/wiki/Osborne_effect http://en.wikipedia.org/wiki/Osborne_effect What killed Perl? An imaginary Perl did.
- oalders 12y ago>> What Killed Perl? The article is entitled "Why Perl Didn't Win", not "Why Perl is Dead". Perl hasn't been killed.
- spacemanmatt 12y agoIt's dead to me.
- bane 12y agoMaintenance. I say this as somebody who loves Perl, quirks and all (actually because of the quirks). It's actually a beautiful language to work in in the same way English is a beautiful language -- it's a beauty because it's a goddamn mess. But it's a rotten language to maintain. Sure, it's perfectly possible to write highly maintainable code (I have a few 30-40k line Perl projects that I can open up and get right to work on without too much fuss) and you can create some coding standards and stick to them, and write perfectly maintainable code. But Perl is a bit like C++ in the sense that everybody has different standards and those standards change and "non-standard" bits of the language start leaking into your code and you spend as much time unmessing things as you do writing code. I don't think Perl will ever really die, it's too convenient, but it's definitely never going to enjoy the dominance it once had. It'll fall back to a very good one-off system admin and log processing language with some extra bits, but it's simply a language that the rest of the world has surpassed and Perl 6 just isn't a realistic offering, after a very loooong wait (nor does it fix the issues non-Perlers have with the language -- it's basically fan service).
- amenbrother 12y agoI was recently asked to add some trivial code to the end of an existing unmaintained Perl script written long ago. Something along the lines of $x = `cat FOO 2>/dev/null`; if ($x == "foo") { system("BAR"); } When I tested it I found BAR was executed no matter what FOO contained without any errors or warnings. WTF? After a little more searching I found the problem was that I should have written $x = `cat FOO 2>/dev/null`; if ($x eq "foo") { system("BAR"); } I have absolutely no patience for this kind of crap, but I don't have time to replace the whole thing right now so I just suck it up and move on. I can understand how Perl may never die completely but I'm never going to use it for anything new.
- shadowfox 12y agoThis sort of distinction exists in other languages though: Java has == and equals. OCaml has = and == etc. (Not that Perl doesn't have its issues; but this is very low in that list imho)
- mattzito 12y agoI think there's some good points in this article - and I relate to it, 'cause this is exactly how I learned Perl. The one other item that I'll add is that some of the characteristics that make Perl awesome for sysadmins, like extremely flexible syntax and the ability to freely access data sturctures in a variety of contexts, can make it more difficult to build proper software development projects. Maybe it's just my limited experience, but it seems like Perl organizations spend a lot more time on mandating coding styles and debating best practices compared with more structured languages like Ruby or Python.
- gsteinb88 12y agoBut as was mentioned in another comment, what you mention as a key appeal for sysadmins is exactly why I can't stand perl. In particular "extremely flexible syntax" makes taking over the sysadmin job from another person, or joining a team, a ridiculous amount of effort. I can't begin to tally the number of hours I've spent with perl code open in one window, and a web browser open to various different perl guides, the documentation, etc. trying to figure out what tricks some script is using that makes it completely incomprehensible to me. Is it fun? Sometimes, except never when a key service is down and you have users breathing down your neck. Or your website is down. Or really, trying to do any kind of maintenance work. And guess what happens? More crazy patches, probably written in an entirely different style! So now there are $n+1$ different styles in that script, and my successor is going to be even more frustrated with me than I am with my predecessors. On the flip side, it's been a great education on the difference between maintaining code for your own use and code in an organization...
- rustyconover 12y agoThe same things could be argued as for why, why C didn't win, or C++ didn't win, or even really PASCAL/Smalltalk/Lisp didn't win. "Winning" is temporary and not the end goal of any language and is best left to be declared by Charlie Sheen like pundits trying to demonstrate their language bigotry. Is Perl the first tool that some of us think of when solving a problem? It might not be for you but it is frequently for me. Ruby might be your first choice, and really that's fine. You're not a lesser or better programmer than anyone else if you choose something besides Perl either. Honestly, if you can solve the problems that you need to solve and you can work with your team, that's the only thing that matters. Not that you're using some language that isn't "winning". As for Perl not having support for recent things like Stripe, that's just silly to argue (the author really should have searched the CPAN). Perl has many new modules, Dancer, Catalyst, Moose, Plack, Starman, Net::Stripe (maintained by me), and full support of AWS's offerings. And, yes modules written in 1999 do get used today, just look at all of LWP. "Winning" isn't everything. Admittedly, Perl 6 isn't out or even moving forward visibly but doesn't mean that the language is irrelevant. Just watch https://metacpan.org/recent https://metacpan.org/recent to see the pulse of the community and the new modules released and updated daily.
- oalders 12y agoIf this article had been written about natural languages, it might be called "Why French didn't win". It may not be the world's most popular language, but it's extremely useful to a lot of people. Winning isn't everything. :)
- jmacdotorg 12y agoArticles which critique Perl as a whole by focusing on Perl 6 always strike me as a bit strange. As someone who works professionally with Perl every day, and starts several new projects using Moose-centric modern Perl techniques every year, the amount of time I or any of my colleagues spend thinking about Perl 6 is negligible. The modern Perl movement, as far as I can tell, arose in part from Perl hackers who started to treat the wandering Perl 6 project — rife with neat ideas, if not with release engineering — as a skunkworks for Perl 5 extensions. In the gap between the middle-aughts and 2014 that this writer waves away with “is anyone still paying attention?” due to no Perl 6 release, the active Perl world adopted Moose, and many Perl-based Moose-driven technologies — Catalyst, DBIC, and so on. These technologies, and the communities around them, have thrived on their own ever since. Nowadays when I think about Perl 6, it is often because I am at a Perl conference and Larry Wall is literally at the podium talking about it and I am like “Well. You go, Larry Wall.” Perl really has reinvented itself in the last handful of years, at least in the eyes of those who make a living inventing new things with it. I can’t call this writer wrong — their perspective is their own. I suppose I can only learn to appreciate the notion that, to hackerly folks who aren’t as ensconced within the modern Perl community as I, the language is this thing from the 1990s that kicked the bucket through one bad decision in the summer of 2000, leaving behind acres of legacy code that’s still being scraped away. To be fair: this indeed describes a lot of what I am hired to do. It’s just that I replace it all with newer and better Perl…
- alien3d 12y agoif ain't php ,think will stick to perl.. first web base language learn..
- alien3d 12y agowhy down vote,since it my first web base language in 2001. By that time,php is new and .net is version 1. When i got visual studio dvd,my pc run slow. So i moved to php and stick till now.
- ww520 12y agoPerl lost because PHP took its place on the web development front. Perl lost because Python/Ruby took its place on admin front. Perl lost because the new version took forever to get ready and broke compatibility with the old code.
- unexistance 12y ago1. True 2. Linux Admin? maybe. UNIX admin? I'd say Perl still on, as it's installed by default (yeah not popular anymore, but a LOT of legacy system still run) 3. cannot comment, as never used new Perl, since UNIX still shipped with old-ish Perl maybe, just maybe it's not just winning & losing :D every language will find it's place eventually.
- ghshephard 12y agoI was a Perl scripter (I never rose to the level of JAPH) from around 1998 to 2002, with my final accomplishment being a two-way HRIS synchronization system between our installation of peoplesoft and our LDAP server (Netscape LDAP server, awesome product). And then I met Python, and I never wrote another line of Perl, and have written some python code almost every week since then. There were two personal reasons why I left Perl. First - I would write some code, it would do what I wanted, but then I would come back in a week (or even a few days) and have no idea how it worked. This is code that I wrote. Yes, I know this is a personal failing (I said these were personal reasons) - but, on the flipside, I've never had anything I've written in Python that I didn't completely understand how it worked any time in the future. Perl just let me write code that was too complex for my brain to comprehend. I blame implicit variables. [edit - and perhaps an over reliance on regex.] Second, If I hadn't used them for a month or so, I used to struggle with Arrays of Hashes and Hashes of Arrays. Once I eyeballed my template, it all came back, but the syntax imposed enough cognitive overhead that I struggled with that data structure (which is one that you use a lot). On the flip side - the very first day I was learning Python, I thought to myself, "What if I just drop an array (list) as an object in this hash (dict), or a dict in this list? Will this work? And it did. Close to zero cognitive overhead. So, that's why I left Perl - Readability and complexity of what should be bog simple data structures.
- stcredzero 12y agoWill this work?...And it did. Close to zero cognitive overhead. This notion of cognitive overhead (or any other kind of overhead) and how it scales (as programs get larger, applications get older, and/or systems become more interconnected) is really what's important to language and system design. Yet most of what gets bandied about between programmers seems to involve what is nifty or what can save you some kind of overhead on mostly rather small scales. Even if a library or language feature can save you from typing another line of code 1200 times throughout a project, that doesn't necessarily mean it's a no-brainer. Ask yourself: What other kinds of costs are incurred? If your nifty doodad increases compile times by a factor of 10, or completely kills the cache across large parts of your application, or makes large swathes of the code hard to debug, it may not work out cost-benefit wise. So, that's why I left Perl - Readability and complexity of what should be bog simple data structures. Ironic in the Alanis sense, because one thing that drew me to Perl in the first place was the bog simple use of Dictionary, as compared to writing the same thing in C.
- stcredzero 12y agoHow does a language win? By being compelling enough to be used for new things. It's not solely a technical concern; it's a concern of the language community and ecosystem. One of the most valuable 4 sentence paragraphs I've read from an HN post in awhile. (Perhaps 3, but the semicolon really separates 2 sentences.)
- twic 12y agoThe semicolon separates two independent clauses, but they constitute a single sentence. When we're thinking about language, clauses are probably a better atomic unit than sentences; clauses are a semantic unit, and sentences are really just a syntactic packaging format for some number of clauses. Just like we should be counting expressions (or something) rather than lines of code.
- stcredzero 12y agoI'll take that comment as a parody?
- twic 12y agoSure, whatever you like.
- stcredzero 12y agoWell played!
- kamaal 12y agoI got introduced to Perl in 2006, at a time when trolls were screaming 'Perl is dead' from top of the buildings. Perl was revolutionary to some one like me who had only done C and assembly language programming. And it turned to be a great tool for the job back then(Processing massive unstructured text files). Its still unbeatable in that area. Back then I saw that people who worked around enterprise projects that used some kind of a relational database used a lot of Java. People who were jumping to the Web 2.0 Bandwagon, used stuff like Python and Ruby largely because of the frameworks. Thereby what's really apparent is tools that are best suited for the job get traction. Perl is still unmatched for many things. Unixy things like dealing with large quantities of text. Gluing things together, getting stuff done quickly etc etc. Perl's every day use cases were going way, as database and web heavy things ruled the business scenarios. Perl largely occupied a niche and ruled it. So is Python today(Web frameworks), and ruby. Also Perl reached a very high peak in the 90's. And reaching that kind of level again isn't possible unless Perl does some very new and paradigm changing. Perl 6 is kind off believed will do that eventually some day. But from what I last heard a few day back in this very forum, there are not close to anything serious even in another 2 years from now.
- overgard 12y agoPerl is sort of like trying to read someone else's brain (in this case Larry Wall's). You get themes and kind of the gist of where it's going, but it never quite adds up to some sort of coherent whole. The defense has always been that Perl is designed more like natural language than programming language, ok, but: natural languages are a LOT harder to learn than programming languages. Put me in a room with Haskell and I'll learn it in a month. Give me a month of training in french and I'll maybe be able to not make an entire ass of myself if I try to get from point A to point B. Human languages are hard. Design wise -- I'm not sure that's what you want to aim for. Almost everything you learn is... surprising. Like flattening lists. Useful in a context, maybe, but is that the kind of thing anyone would ever expect? And why is "list" (@) part of the variable name in the first place? It's like "dynamically typed, kind of, except your variable name has to say if it's one thing or many things or many things referenced with keys". What the fuck? I'd rather the python way of "it's a name that points to a thing, whatever that thing is". GOT IT. Simple. I program in C++ for a living, probably the biggest clusterF of a language ever devised (outside of perl), and the thought of reading Perl still terrifies me.
- stormbrew 12y ago> Put me in a room with Haskell and I'll learn it in a month. Give me a month of training in french and I'll maybe be able to not make an entire ass of myself if I try to get from point A to point B. Human languages are hard. To be fair, I don't think this is actually because human languages are all that hard to become competent (note: not fluent) in. It's just that with computer languages you have an endlessly patient practice partner to work with. In particular, I think the complexity of competent Haskell is definitely higher than most spoken languages.
- yellowapple 12y agoThe idea behind Perl being designed akin to a natural language isn't for its ease of learning, per se, but for its ease of expressiveness. English is probably significantly harder to learn than Python, for example, yet it's likely much easier to write a novel in the former than it is to write one in the latter.
- mantrax5 12y agoIn one of the WWDC sessions an Apple engineer was adamant one should never choose terseness over clarity, because every line of code is written once by one person, but read many times by many people. And funny enough Objective-C is taking this quite seriously, being a very verbose language (the new Swift language also keep the verbose method names, enums and properties). While Perl is exactly the opposite. There's a reason people jokingly call it a write-only language. It has real implication on its usage. You use Perl for one-off scripts you intend to forget and maybe delete after you run them a few times. While CPAN happened, I wonder how much Perl was an obstacle in multiple people joining to work on a single library (versus multiple people just downloading it and using it, big difference).
- mst 12y agoMost of the modern perl ecosystem is libraries built by substantial teams - it's a lot different now than a decade or so ago. The Modern Perl dialect is basically what came out of the new wave of CPAN (Enlightened Perl) movement which is all about using perl's flexibility in a way that scales to larger teams. Sadly, every attempt to explain this to people not already writing it results in a deluge of 'write-only' jokes and nobody bothering to actually look at the code, so while the technical capacity is there, the pop culture nature of programming language choice means people generally never realise.
- mantrax5 12y agoPerl's brand is damaged. No amount of explaining fixes a broken brand. The best that can probably be done is to create a new language which is, say, a clean subset of Perl 6 and call it something new, focusing the message on how readable and intuitive it is.
- narrator 12y agoI always check on indeed.com to confirm the popularity of things. It looks like Python just broke past Perl on absolute job posting numbers. http://www.indeed.com/jobtrends?q=+perl+developer%2Cpython+developer&l= http://www.indeed.com/jobtrends?q=+perl+developer%2Cpython+d...
- autarch 12y agoI suspect that all the languages that are "winning" right now will have "lost" 10-20 years from now too. What's the longest lived language out there right now that's actually still in heavy use? I'd say C. But C has clearly fallen from its position of complete dominance when every new project was written in C (because it was much easier than writing assembly). C++ had its day as well and lives on in many places, but again, it's no longer the go to language for projects where C isn't the right choice. How about Java? It was hot stuff in the 90s and it's still huge today, but it clearly didn't "win". PHP? We'll be living with legacy PHP code bases for at least 10-20 years but does anyone honestly think this will be the language that the startups of 2025 use? Programming is both incredibly faddish and incredibly fast paced. Today's new hotness is tomorrow's "dead" language. Give it 5-10 years and I expect to read "Why Python Didn't Win". I expect we'll see a "Why Ruby Didn't Win" in 10-15 years too.
- icambron 12y agoI agree with your point but not the scare quotes. Yes, the field evolves, priorities change, and languages inevitably fall out of favor. However, that losing is inevitable doesn't make the losing less real, and I think it's still very useful to think about why a language fell out of favor. What changes in priority left the language behind? What could have made it more adaptive? What does that say about current programming trends? In 2020, we may well have a "Why Python Didn't Win" article, and I'll really want to read it.
- kamaal 12y ago>>What changes in priority left the language behind? I'm not an expert but let me try. The most common of all is abstraction level at which problems are looked increase with time. Once the problems you solve get complicated increasingly over time, you run into a situation where your tools have to provide syntax and semantics to deal with that. While the previous complicated things get trivial and easier to deal with. There fore your language has to evolve/grow. This is a double edged sword. If you wish to move ahead and break backwards compatibility to do this, you risk fragmenting the whole ecosystem for very little real benefit(Python 2 - 3 problem). You can keep two system in parallel, plan to support the existing for as long as you can while you work on the new stuff(The Perl 6 Problem). Large changes are difficult to make. Or just stay stagnant and become irrelevant(History if full of such languages). Java is rapidly becoming one such language. Its old, trivial things demand too much code and improvements look like bloat. In the mean while newer languages which have a clean slate to start with come around and stick for a while. Eventually they must face the same problems.
- dmckeon 12y agoAs a Perl and Modern/PBP fan, I have to suggest that CPAN has become a poorer resource over time: >In the olden days, you could expect to find a Perl module for most anything you wanted to do but also: Having 57 modules all called Sort will not make life easy for anyone (though having 23 called Sort::Quick is only marginally better and it seems that every time I look for a useful module on CPAN I find myself in a twisty little maze of packages, all different. TIMTOWTDI, yes, but which one (or several) of the available modules will have a usable combination of convenient utility and mutual compatibility? Over time, CPAN has started to feel like the house of someone who rescues animals, but cannot let go of any of them.
- davewood 12y agoThere are a few things to consider when trying to pick a good/the best module for a problem. - ask in irc.perl.org. it is very likely to get pointers from very experienced people. - use metacpan.org and pay attention to the votes/likes it got. and read the reviews. - each and every CPAN module is automatically tested. look at the stats to weed out problematic modules. - check out the release frequency and when the last release occurred. - read the Changes file - take a look at the tests for the module, is it well tested? are there alot of tests? If you are past a certain point in your life as a Perl programmer this comes very natural and does not take alot of time.
- liotier 12y agoI agree, but naive new Perl users might benefit from some prominent showcasing of well-known good modules or maybe comparison charts between modules in the same functional niche... Maybe that is a subject better left to Perl bloggers rather than to the neutral CPAN, but first contact with Perl is sometimes an embarrassment of riches. Anyway, I love the CPAN - whatever I imagine myself wanting to do, five people have done it already !
- phaylon 12y agoWell, MetaCPAN has a leaderboard of modules, but it could be a bit more prominent: https://metacpan.org/favorite/leaderboard https://metacpan.org/favorite/leaderboard
- steven2012 12y agoI gave up on perl when I saw the following code: $x = $src[$src]; I was confused as hell until I realized that arrays and scalars had different namespaces. That, along with the fact that "or" and || had different precedences were what ended Perl for me. I'm not saying that wonderful code can't be written by Perl, it just wasn't the right language for me in that I hate memorizing one-off rules, which Perl seemed to have plenty of, instead of a language that was more internally consistent.
- oneeyedpigeon 12y agoIIRC, 'or' and || have different precedences in other languages, too - PHP, for example.
- mst 12y agoIf you only want a single namespace for everything, I recommend sticking to only scheme (note: I really love scheme for that property, I'm not being sarcastic). Once you learn -enough- perl, there's a sort of overall consistency that's actually really nice, but there's a gap ... simple perl is very simple, but mid-level perl is generally a mess until you get to the expert level, and then its awesome again. There's probably an analogy to text editors here.
- anko 12y agoI couldn't agree more, and that's why I hate perl. That gap in the middle makes it really hard to hire perl developers unless they are experts. It's hard to find experts because they think perl code is a mess before they get there. It's probably the main failing of perl.
- oscargrouch 12y agoWhenever i read perl code, i feel somebody is cursing me through the source code
- kephra 12y ago> You need large absolute numbers of users to grow a library. That's why library ecosystems like that of Python, Ruby, and Node.js have grown large in recent years. Thats where the author missed an important point. None of those library archives have the culture of PAUSE+CPAN to constrain a minimal code quality when it comes to configuration, documentation, regression test and installation. This minimal code quality is constrained by CPAN testers, when a module hits PAUSE, before the module is seen by the unwashed masses who access CPAN. I've seen many library archives of other languages, but they are all full of junk, undocumented junk, untested junk, and junk that does not configure or install everywhere. The worst example was the LuaRocks system. The quality of the libraries in the Rocks archive had been so bad, that the church decided to remove the module keyword from Lua language, to get rid of this junk. But the code I see for Ruby/Rails, NPM/Node, or PyPy/Python is junk compared to even those Perl modules, that barely managed to convince CPAN testers. You not only need the absolute numbers, but important you need a core group starting the ecosystem who constrain a coding culture. Raw numbers are not enough. A million apes wont write a Shakespeare novel.
- tracker1 12y agoI have pretty mixed feelings on this... I feel that there are more than a few great uses of modules in npm that would never fly in cpan. My biggest issue with node today is that it still relies on python 2.7 for many binary modules.
- spacemanmatt 12y agoI have been so very burned by CPAN module quality in the past. Claims to CPAN 'minimal code quality' ring hollow with me. Apache's collection of Java code is MUCH higher quality on average.
- sharyanto 12y agoTo be fair, CPAN is also full of junk. And Acme::* :)
- danbmil99 12y agoThere are so many snarky things to say, but my mother taught me to never speak ill of the dead.
- pnathan 12y agoAnother perspective: Perl lost because the culture of internet software development moved away from hackers who grokked humor and cleverness towards team-driven business application developers who preferred synergistic framework solutions.
- atmosx 12y agoI think the article is a little bit harsh on Perl. Ruby (1995) and Python (1993) wouldn't probably exist without Perl (1987). Hence IMHO it's just a sort of evolution, nothing more. The other two languages learned from Perl's mistakes and were better designed.
- spacemanmatt 12y agoNo language syntax causes me higher cognitive dissonance than perl. I just find it fugly.
- esaym 12y agoArticles like this make me sad. Perl is a mature, well supported language with a thriving community. It is not in maintenance mode, a new version has come out every year for the last 4 or five years, all with new features, many more planned. Plus the perl conference attendance has been up every year for the last few years. http://www.yapcna.org http://www.yapcna.org You say I should use something more modern? Are not all languages based off of methodologies from 1950? And which one of these modern languages do I choose? Rust, Go, Python, Ruby, Java, JavaScript, node.js, coffee, dart, swift, C#, F#, Scala... Probably many more that I missed but my head already spins. If anyone says they know more than 2 of those languages, then they only know them poorly. I get tired of some new language coming out every year, along with a new community of trolls to bash everything and tell me I need to drop everything I already know to learn their new mess. I must say, none of these languages that are in the news impress me. Yet there are many perl modules that do impress me. I enjoy perl and its community. I like that it is not coupled with any huge corporate sponsorship. It is the bazaar in "The Cathedral and the Bazaar" and that I like.
- vampirechicken 12y agoI never understand the apparent glee with which people perform premature post-mortems on Perl. You never really see people declaring any other language moribund, and then kicking it a couple of times for fun. I don't see the point?
- raiph 12y agoThe domain outspeaking.com is owned by chromatic's company. Afaict chromatic was the first to promote the article with a tweet shortly after it was published and shortly before it appeared here on HN and reddit. When someone noted this connection on reddit and said they thought chromatic wrote it his response was "I'm not the only person with access to the server. Anonymous wrote that article." http://www.reddit.com/r/perl/comments/27o6h5/why_perl_didnt_win/ci32gof http://www.reddit.com/r/perl/comments/27o6h5/why_perl_didnt_... Even if it's not chromatic (I think it is), is it not obvious that the OP article is designed to garner inbound links/views (and sell books) rather than provide a balanced picture? Consider the juxtaposition of the deceitful title and well written content. Do you see what the author did there?
- kbenson 12y agoMy understanding is that chromatic is not the only person at that company that knows Perl, not that has had experience with Perl 6 and/or Parrot. I think it's appropriate to judge the article on it's merits and how well it covers the issue, not the specific views of people that may be associated with it. Truth be told, I was thinking while reading it that it sounded quite a bit like chromatic but with tones down criticism, and said as much to a friend I fowarded it to. I wrote this "Sounds a lot like chromatic when he was disillusioned, but not yet bitter. Which is to say harsh, but definitely constructive." That it's from the company he's involved in doesn't surprise me. If he wrote it and wants to keep it as aonymous, I think that's perfectly acceptable. If someone else there wrote it, that wouldn't surprise me either; I doubt all of his thoughts and opinions happen in a vacuum.
- schmonz 12y agoI recently spent 4.5 years at a big bank developing identity-management tools. They were written in Perl. The first thing I did was screw up in production: http://www.schmonz.com/2014/06/01/tdd-in-context-1-keeping-my-job http://www.schmonz.com/2014/06/01/tdd-in-context-1-keeping-m... So I started carefully making the code testable, then gradually adding tests and refactoring under them, and gradually adopting and taking advantage of Moose, shipping every month all the while. There was never a second screwup. (Will big banks keep choosing Perl for new projects? Yes, for a long time. It's firmly entrenched. It didn't win, but it'll probably never lose either.) Would I choose Perl for a new project? That depends. For programmers with taste, discernment, and discipline, Perl-the-language + Perl-the-CPAN can be incredibly and sustainably productive. For other programmers, it's enough rope to quickly cut off bloodflow to your foot, which you can then use Perl to amputate. In other words, Perl is at the high end of the risk/reward curve. If I could mitigate the risk -- say, by convincing myself that I'll always be in a position to hire great programmers or nobody -- then I'd absolutely want the reward of developing a new system in Perl.