Gianugo Rabellino wrote:
>
> Stefano Mazzocchi wrote:
> > WORA works because the only decent JVM is Sun's (and Sun's clones, like
> > IBM's or Apple's) and Sun has an viral agreement that says that every
> > modification you do, you have to give the code (and the right to use!
> > patent included
On Sunday 17 February 2002 23:25, Stefano Mazzocchi wrote:
>. . .
> Or worse: what if Sun, close to bankrupcy, sells out its java
> division to some company which is much more solid on software
> marketing (somewhere around redmond, anyone?)
>
> Sure, you can count on me writing my own JVM before
Stefano Mazzocchi wrote:
> WORA works because the only decent JVM is Sun's (and Sun's clones, like
> IBM's or Apple's) and Sun has an viral agreement that says that every
> modification you do, you have to give the code (and the right to use!
> patent included!) back to Sun.
>
> But what if Sun c
Stuart Roebuck wrote:
>
> Well, I have to say that I went for Cocoon primarily because it ran
> everywhere and because Java is (in my opinion) much easier to maintain - I
> used to code primarily in C and C++. I realised there would be a trade-off
> in speed to some extent, but to me the trade of
Well, I have to say that I went for Cocoon primarily because it ran
everywhere and because Java is (in my opinion) much easier to maintain - I
used to code primarily in C and C++. I realised there would be a trade-off
in speed to some extent, but to me the trade off is well worth it.
We are de
Stefano,
I had the same idea a week ago. Damn I should be
louder ;)
>I've (finally, some would say) come to the conclusion that WORA (write
>once run everywhere) has to do with Java more or less like it has to do
>with any other programming language in the world.
>
>Despite Sun's marketing.
>
>T
Stefano Mazzocchi wrote:
>This said, I want to throw a stone in the lake and see where the waves
>go:
>
>if Cocoon performance bottleneck is XSLT processing, what about using
>Xalan C as the XSLT processor instead of Xalan J?
>
As long as it is an option, why not ? Personally, I am not yet convin
On Fri, 15 Feb 2002 16:19:42 -0500, Berin Loritsch <[EMAIL PROTECTED]> wrote:
> Lewis, Andrew J wrote:
> > A a user of Cocoon, I think that (provided of course Xalan-J is still
> > supported) this would be fantastic!
> >
> > The ability to include native code in the pipeline as option, at any s
Do you have benchmarks for XSLTC generated bytecode vs Xalan C ?
-= Ivelin =-
-Original Message-
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 15, 2002 3:01 PM
To: Apache Cocoon
Subject: [provocative] resurrecting native code
I've (finally,
Lewis, Andrew J wrote:
> A a user of Cocoon, I think that (provided of course Xalan-J is still
> supported) this would be fantastic!
>
> The ability to include native code in the pipeline as option, at any step,
> makes perfect sense. To not support it makes no sense, and XSLT is the ideal
> can
Stefano Mazzocchi wrote:
> I've (finally, some would say) come to the conclusion that WORA (write
> once run everywhere) has to do with Java more or less like it has to do
> with any other programming language in the world.
>
> Despite Sun's marketing.
>
> Thus, we (Pier and I) have decided bre
; From: Stefano Mazzocchi[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Friday, February 15, 2002 4:01 PM
> To: Apache Cocoon
> Subject: [provocative] resurrecting native code
>
> I've (finally, some would say) come to the conclusio
I've (finally, some would say) come to the conclusion that WORA (write
once run everywhere) has to do with Java more or less like it has to do
with any other programming language in the world.
Despite Sun's marketing.
Thus, we (Pier and I) have decided break the unwritten rule "don't mix
java b
13 matches
Mail list logo
