Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

LAMP++? 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Considering the poor OO support Perl delivers, I'd say that mandating OOP is a step backwards, and hence I'd rather call it 'LAMP--'.
    • Considering the poor OO support Perl delivers, I'd say that mandating OOP is a step backwards, and hence I'd rather call it 'LAMP--'.

      Hmm, I would think that would depend on how far they push that. I guess since the word mandate was used then it is going to be pushed hard. I would say modules should give you an OO interface but how you implement that in the code should not be mandated. Do not restrict TIMTOWTDI (much). : )

  • As a general response to your series of posts, I'll point out the one glaring ommission of Perl which might be considered a cornerstone of J2EE: a transaction monitor/manager (ie, XA transactions).

    While its debatable whether XA is really needed by 90+% of J2EE apps, its the one piece of tech which LAMP/Perl still seems to lack. (LAMP might best be compared to Tomcat, which is kindof J1.5EE)

    As to "what is enterprise", I'll point to this perlmonks thread [perlmonks.com] which kicks the can around wo/ ever really providi

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.