And yet I'm still convinced that the choice of Git over Bazaar has something to do with the smoothness of Github and with "It's from Linus!", the choice of Ruby/RoR with the image 37signals so nicely projects, that JavaScript's recent rise and massive change in perception comes thanks to Douglas Crockford and Erlang would have probably stayed in its niche if it wasn't for CouchDB.
So I was surprised and amazed by the change in perception of Vim over the last year and therefore I blogged about it.
And yes, along your examples Perl faced a similar situation around 2000 (so thanks for the well chosen examples) and decided to do Perl 6 to re-ignite the Perl spark. (Let's set aside for a moment wether or not it worked and what happened after that and boy am I sure the second I hit the submit button people will _exactly_ totally get into this subject.. ;)
I also didn't ask wether or not one really wants the success of the masses or if it might be a good thing to stay in a well-defined niche with a community of your choice, creating your own culture - as for example shows the Linux distribution Slackware very happily year by year and to a great satisfaction of its users.
I also didn't mention how much it might have to do with the age of developers, wether some changes plainly might be a generation thing of "first generation web developers" and "second generation web developers" or how much Apple's regained success does play into all that.
But as we can see within the comments below, old Perl cliches aren't really dead and get repeated all over wether or not the subject was Perl's marketing and not Perl's qualities (or the perceived lack thereof...)
Or maybe we all get kicked our asses by Lisp next year - thanks to Peter Seibel's Practical Lisp Programming book or "Land of Lisp" and of course Paul Graham and Emacs wins all over. ;)
I think it might just be that emacs doesn't lend itself to screencasts or golf quite as much as vim.
Emacs has also had a really strong community for over 30 years (perhaps driven somewhat by the higher education roots). As such, I think it had a more firm underpinning than vim did, so more of the tutorials and such already existed.
I found the tools I went with to be more intuitive and easier to learn than the others. When tools are legitimately pleasurable to use, developers talk about them, and 'hype' builds up.
> Vim's recent resurgence can largely be traced
> to development of Textmate grinding to a complete
> halt.
makes sense - but then why didn't Emacs see an equivalent resurgence (although personally I think Emacs did see a resurgence, not because of Textmate but because of Org Mode). > Git beats seven shades of shit out of SVN.
you could argue the same for Mercurial (or darcs, for that matter). But Git had the better initial marketing, Github, the Ruby folks used it etc. > I cannot think of anything that's changed in Perl
> that'd justify any such interest.
hm, CPAN (and the arguably failed attempts to copy it by other language communities), Moose, MooseX::Declare, Devel::REPL, Dancer, Mojolicious, Task::Kensho, ...And here's some constructive criticism for the aspiring Perl advocate: Stop talking in acronyms and obscure library names. What the hell is Moose and what real world problem does it solve significantly better than the popular alternatives?
Same for CPAN, frankly. Most people younger than me don't get it when you name-check CPAN. What does that stand for?Give me a killer app for CPAN, preferably one that people care about.
Note that the parent post speaks in use cases: Ruby is for problem X, Erlang is for problem Y, JavaScript is for problem Z. What is Perl for, and why won't Ruby work just as well?
How about Django, Evently, Moustache, CLOS, Hackage, Sinatra, Merb, OMQ as acronyms? ;) (None of it Perl..)
Anyways. CPAN _is_ the killer app. It's a HUGE, extremely easy to install module/library archive. Perl's modules aren't spread around everywhere but neatly and nicely collected there and you just do a "cpan Foobar" and get Foobar with all possible dependencies included.
Which is something what many languages (some still don't) have these days one way or another but really nothing compared to CPAN in number, service, search, testing facility and so on. You plainly _never_ have to bother searching your ass off to find some library you might need.
Moose is Perl's OO system - as with JavaScript you can do different OO styles with Perl and Moose is a framework to do a role/trait based (please see Smalltalk for details or Perl 6's spec) OO with a heavy twist on metaprogramming.
Perl is for writing things like Amazon or the IMDB and keep it running for 12 years in a row or for creating Nagios and SpamAssassin to watch over half of the Internet. Thanks to Perl, everybody can easily imagine what push, pop, shift, unshift on Arrays/Lists does and thanks to Perl everybody has very shiny Regex these days. That's why Vim has a magic/nomagic flag and what the P in PCRE stands for. The Ruby world gladly thanks Perl's DBI after which it modeled its own database interface.
That's what Perl is about. Sharing shiny features and establishing a culture of "getting things done who run really fast".
Now.. CPAN.
Let me explain my latest round with fighting Perl/CPAN. I wanted a perl interactive mode. When I want to test out something in Ruby I use irb. In Python, I can type in `python` and enter interactive mode. Even PHP has a rudimentary interactive mode now.
So I try looking at `perl --help`. Nothing there. So I turn to google and find that I need a REPL whatever that is. So I try to figure out what a REPL is. Find that. Now I find that I need to run a little script to run Devel::REPL. Doesn't work. So I load up CPAN and type in `install Devel::REPL`. No less than thirty minutes later, 150 or so screens of noise, and at least 25 questions that I have to hit [enter] for I get a failed install. I have no clue what failed -- something to do with tests (the error is 4 screens back in the middle of even more text) so I try to force the install. I'm now 45 minutes into this and finally get Devel::REPL installed. I fire up re.pl and I get `SCALAR(0x100b81070) is not of type SCALAR at /opt/local/lib/perl5/site_perl/5.8.9/namespace/clean.pm line 56`. All of this for a feature that should come with a base install.
This is just one example of why I avoid perl as much as possible.
If you want to email me (address in profile) I'd love to figure out what went wrong so nobody else has the same problem in future.
perl -de0
which still seems to work.
Perl was the hip thing back when those projects were being developed. If they were being made today, it's overwhelmingly likely that Perl would not be used (see Facebook).
Sounds like Ruby's Gems: http://rubygems.org/ or even python's PyPi: http://pypi.python.org/pypi ...
And most importantly: It provides you globalized automated testing on a variety of systems of anything you upload, through CPANTesters.
Just as an example: I uploaded a module yesterday and now it has 38 tests on as many different configurations already: http://matrix.cpantesters.org/?dist=CGI-Application-Plugin-T...
So not only gives it a very useful and otherwise extremely expensive tool to you, the developer, it also shows you this information about other modules, so it lets you gauge the quality of the modules you are considering to use.
Edit: Also, as an additional goody: The testing culture of CPAN allows development of ancillary tools that analyze the current state of CPAN and highlight modules that are having issues with their tests: http://analysis.cpantesters.org/ This can help generate bug reports for developers who don't have time to figure out exactly why a test failed on an obscure combo and they provide an in for CPAN-Newbies by pointing out to them which distributions could use patches.
Haskell's system is called "hackage" for example and "R" has its "CRAN" and so on.
Though it's really no fair comparison as CPAN contains what.. 89033 modules? http://search.cpan.org/
I'm not very familiar with PyPi since I'm not a Python programmer, but Gems pretty much work exactly like they should. Especially when you throw RVM into the mix.
89033 modules
Only 21694 distributions, though. The analogue in Ruby is a gem and RubyGems already has 19502.Note I didn't say there is not such product/framework, just, as the articles says, they are not promoted/known.
There's a whole bunch of them, with different design goals or philosophies.
[edit] I'm gonna pick a little bit on Catalyst and do a quick surface review at website level from a non-Perlist POV.
Homepage : ok, looks nice.
Documentation : uuh ! Dry redirect to CPAN. First impression before reading, it's not the doc, it's the API doc. Ah, wait a second, it _is_ the doc. Not very appealing and some things are so not obvious that it takes a note to understand it like "Note: Click on the heading in the previous line to jump to the actual chapter. Below is a "table of contents" for this chapter."
Download : Again directly to CPAN, at first sight confusingly looks like an API doc. For newcomers not versed in Perl it is not very friendly.
Community : not much to say, a good wiki with apparently interesting stuff to read. But the first thing you see is that the "Why Catalyst is an excellent web application framework?" is an empty page.
The perl community has every reason to be proud of CPAN. It's great tool but it's not the answer to everything. It's all therem but it lacks the last mile, the 20% of polish to make it a tad more friendly/attractive.
It's the whole point of the article I think. It's not to criticize Perl, just to say it needs a better marketing strategy.
Why do people keep trotting out this stupid pointless number. How much of that is duplication? How much of it is crap? How much of it is literally toys (e.g. ACME stuff)? In any case, Java has vastly, vastly more so any language that runs on the JVM automatically beats perl here.
99% of programmers will never notice any functionality missing in Ruby or Python that CPAN has.
Metcalfe's Law. The value of the CPAN increases dramatically with every addition, especially because of the maturity of the entire CPAN infrastructure: CPAN testers, CPANTS, annotations, reviews, dependency tracking, BackPAN tracking, gitpan, linked documentation, et cetera.
Demonstrably nonsense. Let me add a new module called ACME::DoNothing. What have I increased besides disk space and a meaningless module count?
The testing stuff is good and it's the direction everyone should be going but not having it obviously isn't too much of a problem because so few systems currently have it (CPAN was successful long before it had it as well).
You can't really draw that conclusion. Other systems do not have it because it is not an easily solved problem, not because they do not think they need it.
Also, needing and benefiting from something are two entirely different things. Yes, no language actually NEEDS this kind of thing. But a language that has it is literally self-healing, since any kind of problem, be it breakages from dependencies, cross-platform issues or core language changes are communicated very rapidly to the developers without them even needing to make an effort.
The Perl 5 Porters mailing list has automated mailings which test CPAN against bleadperl to discover which, if any, commits break existing CPAN distributions. This helps p5p revert genuine mistakes and CPAN authors to patch their bugs.
I know that several minor revisions of other languages have broken several popular extension libraries.
Given human penchant to slip up and not realise problems until after they are encountered, having tests makes pretty much the difference between "science" and "hypothesis"
The fact that the cross product of several generations of interpreter, several platforms, and tens of thousands of distributions is generated automatically by a handful of volunteers is a strong argument for CPAN/Perl being unique amongst the dynamic languages in it's testing and compatibility.
Additionally, people who aren't in the right circles probably never know how much grepping through CPAN happens when new features and syntax is suggested for the core Perl5 language. All done by the porters to be sure that new syntax won't break existing code without some fore-knowledge. This is on top of the automated testing.
CPAN is the only reason that I've kept my Camel book around since 2000, hoping that "someday" I'll learn Perl.
Oh, and "It has MOAR!" isn't really a good argument. I've authored two gems, I think. Those are the only two times in two years of using Ruby that I haven't had the ability to just install the library that I needed.
(I loved Perl for years until I found Ruby, then never turned back...)
Maybe it's a question of perl putting a lot of things in CPAN versus other languages putting more in the standard library?
Have a look at cpanminus (http://search.cpan.org/dist/App-cpanminus/lib/App/cpanminus....). Its a lightweight and JFDI alternative to the default CPAN client.
Maybe it's a question of perl putting a lot of things in CPAN versus other languages putting more in the standard library?
Swings and roundabouts really because there is no definitive advantage in either approach.
Advantage in CPAN approach: Its more darwinian. Your libraries are more up-to-date (stdlibs often get stale)
Advantage in stdlib approach: Less dependencies. Batteries included out of the box.
After installing Perl first thing I do is load a few important CPAN modules (like Moose, AnyEvent, Coro, Devel::Repl, DBIx::Class) and then all your big loads are pretty much done.
> And here's some constructive criticism for the aspiring Perl advocate
point taken, thanks.Perhaps the Perl success stories should be mentioned more often, too:
Want to launch a one-man search engine? Perl makes the easy things easy and the hard things possible: http://www.gabrielweinberg.com/blog/2009/03/duck-duck-go-arc...
Amazon.com, del.icio.us, Craigslist, the BBC? All have significant parts written in Perl: http://www.fischerlaender.net/perl/perl-used-for-web-develop...
:P
a) emacs vs. vim has been a holy war that has gone on since both were conceived and is a debate which is often older than the programmers discussing it. To be ignorant of recent language developments or internal acronyms is excusable, to be ignorant of vim/emacs is less so.
b) emacs and vim are not specific to any one language. Dropping acronyms that are non-specific to the topic (perl vs ruby, python, whatever) doesn't have some domain specific knowledge attached to it. If you're on either side of the debate, vim can be equally familiar or obscure.
Complaining about an article on perl.org not mentioning what CPAN is, is like complaining about an article on cars.com not mentioning what BMW is.
I haven't used perl, but I do use ruby and I'm learning haskell. What does CPAN do that make rubygems and cabal failures? They both work really well from what I can see (especially cabal), but since I don't know perl, my POV is obviously limited. What am I missing out on?
Sorry for the misunderstanding.
Counting a library's worth by the number of things in it is probably not a good measure of its worth. But it'll be who knows how long before pypi or gems overtake cpan in terms of sheer quantity.
A better measure of worth would be a deathmatch showdown between seasoned perl people and seasoned ruby/python/whatever developers, where each can bring the powers of his libraries to bear.
But anyone who has had much exposure to perl people will tell you: never, ever underestimate them. They'll come at you with solutions to problems out of left field that solve the problem in 34 characters of self morphing regular expressions or something while everybody else is turning in comparatively huge 8 line readable programs.
Until other languages reach this kind of solidity and thoroughness in testing CPAN will stay at the top of the bunch.
Programmers are just likely to want to follow fashions as tweens - it's just that they're not so likely to admit it.
EDIT: (we're) not so likely to admit it.
The buzz, the screen casts and other errata are a consequence of a lot of people making the same logical, reasoned choice and talking about it in public. I cannot think of anything that's changed in Perl that'd justify any such interest. I admit that may be my ignorance. Making sexy screencasts might get a little traffic but you can't astroturf wave of developer momentum with them.