> > I've been investigating
> > http://marc.theaimsgroup.com/?l=xalan-cvs&s=xsltc a bit and it seems
> > like there are some people actively working on it. Only Sun-people
> > however
>
> 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?
My understanding is that there are currently several IBM folks working on
the XSLTC base from various aspects. Some (all?) of the code checked in so
far is on a branch. Our intent is to be quite active in XSLTC development,
evolution, and maintenance.
As far as Mike's comments about conformance, I believe that is getting much
better.
-scott
Stefano Mazzocchi
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
rg> cc: (bcc: Scott
Boag/Cambridge/IBM)
Subject: Re: [FYI] Profiling Cocoon...
10/09/2002 04:44
AM
Please respond to
cocoon-dev
Quoting Steven Noels <[EMAIL PROTECTED]>:
> >> I'm not saying we shouldn't be bugtesting for XSLTC, it's just that I
> >> don't know if the XSLTC community will be there to follow up on our
> >> bug reports.
> >
> >
> > I hear you. Consider it a stress-test of both the software *and* the
> > community around it.
>
> I've been investigating
> http://marc.theaimsgroup.com/?l=xalan-cvs&s=xsltc a bit and it seems
> like there are some people actively working on it. Only Sun-people
> however
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?
>, 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?
> > 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.
> > And if this thing doesn't work out as expected, we can always ship
> > Cocoon 2.1 final with Xalan enabled.
> >
> > What do you think?
>
> Fair enough. We'll be a prime beta test site for both Avalon and XSLTC.
At one point, Sam Ruby was very puzzled by the ability of the cocoon
community
to work with so many different projects and all of them on the bleeding
edge
and still being able to manage not to piss off users every day.
That lead to the creation of gump which pretty much shows that that earlier
hidden contracts are made visibile, the solid the whole net of contracts
become.
> 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.
--
Stefano Mazzocchi <[EMAIL PROTECTED]>
------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
