I suppose that someone with vast experience in Bugzilla rewriting it in another language in which he's well versed will probably come up with something quite nice. The same guy rewriting it in Perl will almost certainly come up with something at least as nice.

It's tough on the psyche to pound your forehead against the same frustration day in and day out, and it's a perfectly normal reaction to come to detest not only the frustration itself but everything associated with it. Normal, but irrational. The wise course is to delay action until after the (normal) irrationality passes.

Most of his arguments seem to be that Perl is not and was never intended to be a bondage and discipline language. I can understand how alluring a B&D language can appear to be after wading through a bazillion lines of poorly written legacy Perl code... but then, after wading through tens of bazillions of lines of poorly written legacy B&D code, Perl looks like the girl next door with a righteous buzz on and no plans for the rest of the weekend.

What it all boils down to, I think, is that the poor guy's frustrated and is looking for a way out of his frustration.

Bugzilla x Perl

<meta>
lorn, I see you're Brazilian and that English is not your mother tongue. No problem: neither is it mine. As far as the Subject above goes, I think you mean it as a shorthand for "Bugzilla for Perl": isn't it? If not, then I stand corrected and you can safely ignore the rest of this post. Now, as a general rule l33t IM talk is discouraged here and personally I would recommend against adopting it at least in subjects. However, if you really want to use that, in English you probably don't want "x", but "4". This is all a wild guess based on the fact that in Italian we also use "x" for "per", which actually stands for "for". No pun intended, but not avoided either. ;-)
</meta>

My intention was to say "Bugzilla versus Perl" but, thanks for the tips :)

Lorn
-http://lornlab.org
-slackwarezine.com.br