cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Noels <>
Subject Re: [FYI] Profiling Cocoon...
Date Wed, 09 Oct 2002 10:55:43 GMT
Stefano Mazzocchi wrote:

> yes and, admittedly, this sucks from a diversity of community perspective. But 
> should I remind you that Xalan suffered more or less the same problem for at 
> least 18 months?

Nope - and IMO, the *core* tools are still quite heavily 
'supported' by Sun or IBM. Dunnow how this is at the other side of the 
pond (Jakarta, especially Tomcat).

Oh well - I'm in a rant mode these days:

>>, and I recently organized an XSLT seminar with Michael Kay who 
>>was quite 'amused' w.r.t. XSLTC compliance & partial performance 
>>optimalization of XSLTC. But he's obviously biased :-)
> Can you please elaborate more on this?

No bare facts to support this, sorry. It was something he muttered upon 
my questions on XSLTC.

>>>Anyway, just a reminder: you never get people to scratch if you don't 
>>>create some itches :)
>>Would that be itches or just pet peeves? ;-)
> I think nobody here gives a damn about what XSLT engine they are using as long 
> as it's fast and compliant. I'll leave ego fights to those who still enjoy them.

Hey, cool down ;-)

You and Ivelin have been advocating XSLTC for a long time - and I value 
your effort doing so. But we are allowed to make jokes, no?


>>I believe we should definitely start warning people upfront that they 
>>really should stick to release versions, instead of relying on CVS 
>>checkouts of HEAD/2.1-dev - for some reason, there's quite some people 
>>using CVS instead of our release version. But that's another rant.
> I think that a WARNING page is enough for people that want to try things out 
> and know where we are heading and planning in advance. And I think they know 
> very well the cost of rewriting things when something change under your feet. 
> The use of open source software is partially because of that.

Nope, it's not enough. A lot of people are using daily CVS builds as 
development/production infrastructure, which is good for bugtesting, but 
also brings an enormous amount of 'this was working in CVS of 
dd-mm-yyyy' mails to the list. They should be motivated to use stable 
builds instead, maybe by backporting some of the nicer 2.1 HEAD features 
to 2.0.3.

Steven Noels                  
Outerthought - Open Source, Java & XML Competence Support Center            

To unsubscribe, e-mail:
For additional commands, email:

View raw message