on 1/27/00 2:28 PM, Isaac Reuben <[EMAIL PROTECTED]> wrote:
> The downside of multiple concurrent languages is that any feature/change has
> to be implemented in all the languages to maintain compatibility, forcing us
> into the lowest common denominator, and not letting us use the unique
> features of ANY of the platforms. And if we aren't maintaining
> compatibility, then what's the point?
Well, that is up to the maintainers, correct? If there are people willing to
do this work, why not allow it?
> Are the java-based options really THAT much better? If so, then should the
> whole project move to be java-based? If java DOESN'T provide significant
> benefits, then does focusing on only php (so we can use it's unique
> features) make the most sense?
That isn't the question, the question is what you have skills with.
Personally, yes, I do think that java based options are better than PHP at
this point because of so many features that you gain from the servlet api
vs. PHP. But, that doesn't stop me from thinking that PHP is also a good
solution and having its place in the world. If all of your developers only
know PHP, that also makes it the best solution for you. We want to give
people the options and options are a good thing.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
