At 09:45 12/4/01 -0400, Sam Ruby wrote:
>Peter Donald wrote:
>>
>> Welcome to opensource! Standards are not done here - we can implement
>them
>> but we don't build them - for those please go elsewhere
>> (IETF/W3C/JCP/Other). One of the advantages of opensource is people are
>> free to adapt them to their own environments. Hence they do. If you want
>> static versions go buy something from a major vendor.
>>
>> Have a look at all the projects under apache umbrella. Now rate the
>> activity of each project excluding people who get paid to directly work
>on
>> products. Now correlate this with cost of entry (of which jars in CVS is
>a
>> factor). Excluding ant for the moment what do you see? ... Which ones
>have
>> more community behind them? Which ones store binaries in CVS?
>Coincidence?? ;)
>
>Best community, by far, IMHO is http://www.php.net/. The number of active
>developers there is larger than the total number of developers across all
>Jakarta and XML projects combined. No .jar, .exe, .so in CVS at all.
right - and I assume very few similar projects also include exes/dlls.
There is a number of reasons for this
* c/whatever is infinitely more mature than java as a development environment.
* sos/dlls/exes wouldn't work as I assume php is built on multiple
OSes/architectures/environments
Notice however that most of jakarta is based on java and it's immature
environment and java is cross-platform so these steps are viable ;)
>PHP 4.0 was essentially a rewrite, with a high focus on backwards
>compatibility. PHP 3.0 was essentially a rewrite with a high focus on
>backwards compatbility.
I am not sure what this has to do with above - but ... the question arise: so?
As products become mature they stabilize - that is natural. PHP reached
that plateau, ant sorta did with 1.3 and really will with 2.0. Many of the
other projects are a work in progress with no real reason to maintain
eternal compatability. In most cases (ie turbine/avalon/cocoon2 are the
ones I am aware of) it is less cost to move to a better system than it is
to stay with a sucky system.
When/if any of these projects gain thousands of followers this tide will
turn but until then ...
>Not because a standards body dictated it. Not because a major vendor paid
>for it. But because it was the right thing to do.
you mean PHP matured?
>CPAN wouldn't be possible if Perl were as unstable as most Jakarta
>projects. While outside of the Apache umbrella, Perl is another example.
So how long has perl been around? What about the apache projects? Where the
early years of perl bump free?
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
