« It's been in my head, too! | Main | »

February 08, 2011


Feed You can follow this conversation by subscribing to the comment feed for this post.


Ben, I totally agree. It's both a blessing and a curse.




This is actually one of the reasons behind the creation and promotion of Task::Kensho ( http://search.cpan.org/dist/Task-Kensho ). The end goal was to build a kitchen-sink included Perl, but that has been delayed.

The idea is to create an opinionated Perl distribution based on perceived best-of-breed distributions. Things like Moose, Catalyst, DBIx::Class, etc are included.


Indeed, this is one of the primary differences between Perl 5 and Perl 6. Perl 6 still has a great deal of flexibility underneath, but we've gone out of our way to make sure you aren't required to know about it; instead, we've chosen sane defaults for most of the areas where Perl 5 forces the user to make a conscious choice.
If you love Perl because it matches the way you think, and if that's because it's also the way I think, then I think you'll love Perl 6 even more, once we get a few more of the kinks worked out, and distribute the future a bit more evenly.


What if the standard is not good enough? Then people would want to improve on it but might be held back because they don't want to break a standard.

So a lack of standards, for such things at least, might be good for innovation.


@hanekomu: Yeah, but--my gut is that if a language accumulated enough junky standards in the core, then it just wouldn't be popular, and no one would care about using it, let alone innovating on it.

Whereas the tl;dr version of my post above is basically: 1. there's a ton of stuff I love in Perl; 2. I wish there were more of what I love about Perl in the core (i.e., that more of the philosophy & language design that's gone into Perl, so far, would be extended to the other areas that I miss when moving from Python to Perl).


@TimToady: Thanks for the note, Larry--I'm looking forward to trying out (and loving) Perl 6! If it can take what I love about Perl, and bake additional sane decisions re: language design into the core, then I'm really optimistic.

Kevin G.

I was walking down the street today and this post came to mind and I realized I was burningly curious about one thing: when you opened a file and started typing Perl code for the first time in months, was there anything in particular that made you say "Ahhhh, I'm back in the land of _____"?


Hey Kevin! You know what it was, specifically? It was that I wanted to raise an exception (an actual named exception) without having to introduce some new dependency on this module I was writing, many of which dependencies would also end up pulling in all of Moose, which I wasn't particularly crazy about, and which dependency would almost certainly be different than what someone else (some application that might use my module) was using for raising exceptions. (There were other things, too, like pulling in Object::Tiny just to get simple objects with accessors, but iirc, it was the exception case that made me throw up my hands.)


I easily learned the Perl programming language. The book has been umpteen only.

Kevin G.

Ah, of course, and well put. But I was actually curious about, and my fault for not properly enunciating that the "Ahhh" was actually meant to be an "Ahhh" of satisfaction, relief and happiness rather than an "Aarrrgh". Was there any nice thing that immediately jumped out at you from being back in Perl-land? Some nice Perlishness that you missed in Python? I was just curious, and we should be fair, you know.


Yeah, that's an interesting question... it's hard for me to pinpoint something specific, because it's more just a general feeling of comfort that I get when I write Perl: because it's so native, and it's kinda the default for how I think when I'm coding, I find that I don't ever have to think about syntax--I can think entirely at a different level re: how the code should work and fit together. I like being at that point with a language, and it's why Perl's still the language I choose most frequently for prototyping.

The comments to this entry are closed.