It looks a lot like "the grass is always greener on the other side of the fence" to me.

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.


In reply to Re: Bugzilla x Perl by gloryhack
in thread Bugzilla x Perl by lorn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.