Throwing in my 2c. -1 for me. P5EE, along with Certification, is the
third rail of Perl: touch it and die. Enterprise computing platforms
are a tad more than then web. While I applaud Stephen's efforts to get
something out of the door, the result doesn't feel right. If I could
quantify it, I
Throwing in my 2c. -1 for me. P5EE, along with Certification, is the
third rail of Perl: touch it and die. Enterprise computing platforms
are a tad more than then web.
What do you mean by 'touch it and die'?
Is it some sort of 'boogie man'?
While I applaud Stephen's efforts to get
This should have gone to the list as well
---BeginMessage---
On Thu, 2002-08-29 at 21:40, Nigel Hamilton wrote:
What do you mean by 'touch it and die'?
Is it some sort of 'boogie man'?
Yes, it is a boogie man. As yet I've not seen any general consensus on
what p5ee actually should
James Duncan writes:
Yes, it is a boogie man. As yet I've not seen any general consensus on
what p5ee actually should do; it seems a little premature for voting on
a code-base for the *enterprise* edition of Perl.
What about Java's write once, run anywhere. It still isn't true.
Marketing is
On Thu, Aug 29, 2002 at 05:02:39PM +0100, James Duncan wrote:
On Thu, 2002-08-29 at 21:40, Nigel Hamilton wrote:
What do you mean by 'touch it and die'?
Is it some sort of 'boogie man'?
Yes, it is a boogie man. As yet I've not seen any general consensus on
what p5ee actually should
On Thu, 2002-08-29 at 17:52, Rob Nagler wrote:
James Duncan writes:
Yes, it is a boogie man. As yet I've not seen any general consensus on
what p5ee actually should do; it seems a little premature for voting on
a code-base for the *enterprise* edition of Perl.
What about Java's write
I don't think it makes much sense to have a code base called P5EE. That's just
not the way the perl community works. Perl is too flexible to be put into a
straitjacket like this. And forward motion is not by itself justification of
forward motion. Standing still can be better than going in the
James Duncan writes:
Yes, it is a boogie man. As yet I've not seen any general consensus on
what p5ee actually should do; it seems a little premature for voting on
a code-base for the *enterprise* edition of Perl.
What about Java's write once, run anywhere. It still isn't true.
James Duncan writes:
But who is going to market P5EE?
No one, but it still has to have a name. P5EEx::Blue is just too hard
to pronounce.
is all valid stuff -- I don't think however, that it can become the
signed, sealed and certified P5EE.
Who has the authority to sign, seal and deliver
Adam Turoff writes:
From that page, I don't see any concrete details on what features
are found in an enterprise system, which of those features are
lacking in Perl today (if any), and why this lack of features needs
to be addressed with P5EE.
In J2EE, they have tried hard to provide:
10 matches
Mail list logo
