Glad that you raise that issue. But it wasn't as harsh as it may seem. I mentioned the kickoff episode to have an intro, but took those words out of context to get a short intro which would defend somehow my case of instigating a discussion about templating, forseeing that I would be bashed with do your homework or don't reinvent the wheel or choose Foo::Bar, it does the job or such.

The truth is, those words were uttered likewise, but theres's more about it. As the inhouse SAP administrator at that time I was asked to program the fallback for the applocation our 'Java Witnesses' had been struggling with for more than a year. It was a changing team, mostly students, and they ended up with a myriad of classes they couldn't handle any more. As they went along, I often asked "why don't you do that in perl?", and as the final deadline drew near they gave in and confessed they couldn't, alas, a bit too late.

I left away the question "Can you do that?" and my answer "I don't know, but I assume yes. I'll try". I did, not in 5 but in 8 days. I omitted this conversation to avoid getting posts saying you fool, you agreed having no clue.

Yes, the application is crappy, but only in what concerns the SAP part - a plain nightmare, but that's SAP. The web stuff is straight forward, plain CGI as well, with a dispatch table resembling CGI::Application (which I just oversaw at that moment) with heavy use of AutoLoader.

After all, this situation was non-standard, but a great raise in esteem for perl and your humble poster. The company is more than OK in its standards, generally. Otherwise, I wouldn't be there any more.

At the end, it showed again that "one perl is often more worth than a sack of java beans", just to quote myself ;-)

greetings,
--shmem 

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

In reply to Re^2: RFC: Templating without a System by shmem
in thread RFC: Templating without a System by shmem

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.