I disagree that these all mean the language is too difficult for beginners. It might be easier to learn a language with a small core syntax (like C or Python), but to do useful things you'll also have to get to know libraries and extensions, just so you can do something useful.

You'll never find a language that allows you to Do Useful Things without having to learn a few things here and there.

The same goes for natural language. You can go to the Cairo Bazaar (presuming you don't speak Arabic) and buy some things by pointing and holding up fingers and occasionally flashing the appropriate number of Egyptian Pounds. You'll have a more difficult time getting directions to your hotel if all you can do is point and grunt.

Granted, some people aren't interested in having to learn much. And, granted, there are parts of Perl that frustrate me (the tricks you have to go through to inherit instance data in objects, for one).

The thing that bothers me about articles like this is the idea that there's some terrible, hideous complexity lurking underneath Perl's friendly Do What I Mean facade, and that's somehow inappropriate for programmers. That's simply a matter of education -- especially when dealing with the second great hurdle of Perl, the difference between scalar and list context.

Hello chromatic,

Your points are well taken and valid. As the "Warts and All" article was the latest part of a now 22-part series on Perl, I think it goes without saying that the piece is not intended to scare newcomers off the language.

Rather, those following the series have gone through a topical survey of most of the major Perl subjects -- enough to get them going writing a variety of web-based scripts. This article is like a signpost along the way, saying, in essence, "now that we've covered most of the basics, here are some things to watch out for". Necessarily, these include opinions.

Which, again, needs to be considered in context: the series itself is titled "The Perl You Need to Know", and it has a specific conceit -- teaching Perl to developers who are goal-oriented and want to achieve a particular task, without delving more than necessary into the academics of the language.

I fully understand that the latter point probably makes many Perl Monks cringe and shriek. I sympathize. But much as you, and I, possess interest in programming and in Perl that goes beyond merely "how do I accomplish such-and-such and move on with my life", not everyone shares that same depth of interest. They may have perfectly valid reasons. I don't feel that it benefits the Perl community to alienate these people, or to suggest that only those who want to "go all the way" need apply.

In any case, that is the philosophy behind the "Perl You Need to Know" series, and I thought it might help to put installment 22, "Warts and All", into context.

Once again, I do appreciate this discussion and all of your wisdom out there.

thanks

Aaron

My brief exposure to Python came when I was called on to maintain a suite of programs written by someone else. It was a useful experience. I have respect for the language and the people who use it.

Now that I've paid my compliments, I have purchased the right to turn critical - (just kidding).

What's wrong with Python is the same as what's wrong with Perl. Not all of its advantages are always available all of the time - some features exclude others (like, nobody writing a one-liner on the command-line would regard significant whitespace to be a positive feature in that application; but, nobody likes trying to read a clutter of unfamiliar perlvars ).

So, I do think there was a slight unfairness to the article, if you don't mind considering the observation. In the earlier articles beagle, you folks said to Perl, "Be a square!", and then "Be a circle!", and behold, Perl was adaptable to being both. Then, in Warts..., I think you've said "Aha! but Perl cannot be a square and a circle at the same time!" (Which is true - but, I have heard rumors to the effect that Larry considers it a bug, if a circle cannot also be a square, and intends to do something about that!)
:-)

mkmcconn