GOMEZ Henri wrote:
>
> Hey Sam (Rubys) what's the IBM position on this project ?

I've been trying to stay out of this particular discussion.  Personally, I
agree with James Cook that Jon is doing an excellent job of alienating
people.

Once upon a time, Craig was the lone heretic.  The fact that he was
outnumbered at the time was not relevant then, nor is the fact that Costin
appears to be outnumbered now relevant.

The 3.x series have certainly received a lot more performance focus up to
this point.  Reservations have been expressed as to whether the cleaner
architecture would ever match the performance of 3.x performance. From
watching the commit logs for 4.0, it looks like the focus is still on
completeness and correctness at this point.  I expect this to change as the
code moves towards release and possibly (probably?) into the first couple
of dot releases.

I would very much prefer this discussion to be based on technical merits of
the various baselines.

> Did there is a kind of Yalta on ApacheGroup and who do what :
>
> IBM == xml.apache.org and SUN == jakarta.apache.org
>
> That's my point of view !!!!!

That is not my point of view.

Most of us are not independently wealthy, so we work for a living.  A few
of us are lucky enough to be paid to work on open source.  In my case, I am
further blessed in that I have a significant input into which projects I
wish to pursue.  Because of this, I've have made a number of minor
contributions to several XML projects.  However it is worth noting that I
have made more significant contributions to Jakarta projects, in particular
during the first half of this year.

Costin once was paid to work on Jakarta, now his "day job" has resulted in
improvements to xml-xalan.  Furthermore, it is clear that Craig would work
on Catalina even if Sun didn't pay him to do so.

Meanwhile, IBM does ship a number of Jakarta projects as a part of
WebSphere.

The lines are not crisp, and are constantly shifting.  Both IBM and Sun
believe strongly in XML, Java, and Apache.

- Sam Ruby

Reply via email to