Re: Kill this thread (was: Relative Speeds of XSL Engines Java v s. C++)

[Ovidiu Predescu <ov...@cup.hp.com>]

Simon,

I think you got me wrong or you must have read somebody else's message. I never
said Cocoon is not a viable technology because it's Java based. (I'm actually
using it myself in some of the projects I work on.) I just said that for
implementing simple, algorithmic programs, C/ Objective-C/C++ will almost
always be faster than Java, given a good compiler implementation (GCC will do
it).

I totally agree with your earlier points that code reuse in Java is much better
than in C++, for example. Also C++ is a poor choice IMO for developing large
scale projects exactly because of its strict enforcement of language rules. I
always used Objective-C, and now Java, instead of C++ for such projects.

I believe you're preaching to the converted here, I'm using Cocoon and Java on
a daily basis for quite some time now. And if you carefully read my original
reply you will notice my above points.

Regards,
-- 
Ovidiu Predescu <ov...@cup.hp.com>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://www.geocities.com/SiliconValley/Monitor/7464/

On Tue, 6 Feb 2001 22:07:53 -0800 , Simon Waddington <si...@viafone.com> wrote:

> > Ridiculously off topic no?
> 
> Obviously I thought not, I was merely explaining why Cocoon is an excellent
> example of why Java is a good language in spite of some apparent, but not
> necessarily important limitations.  I've seen many, many people look at
> Cocoon and its component technologies and conclude, often quite publicly its
> not a viable solution because its Java based.  
> 
> In the absence of a non-advocacy policy I'll feel free to counter such
> conclusions and explain why perhaps Cocoon is quite the opposite - an
> excellent example of code reuse and leveraging of many highly appropriate
> features of Java to achieve the goal without having to worry excessively
> about performance.
> 
> As for email I don't think is interesting, no offense intended, but the
> delete or ignore thread button has always worked for me.