Absolutely right. You take a good standard tool with all those
"Getting Started" and other gift ribbons and rush in. And in a
year or so new enthusiastic guys making their careers in that
company decide to produce something different - and you stay
alone with your stuff getting obsolete and far from the way.
Absolutely right.
-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet API
Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Justin Wells
Sent: Friday, January 28, 2000 1:00 AM
To: [EMAIL PROTECTED]
Subject: Re: New article: "The Problems with JSP"
Quoting Nic Ferrier ([EMAIL PROTECTED]):
> I personally would not suggest using a non-standard tool for a big
> rollout project that is going to need continued support -
Really? You wouldn't use Apache? Or Linux? or PERL? Ever?
I don't think standards are all that important when you are talking
about opensource applications. The relevant question then is what is
the size of the userbase, since that determines your level of support.
(ie: the more there are, the more people there will be fixing and
helping other people, and the more people there will be to step in
and take over if the initial developers leave.)
Justin
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
