Jason Hunter writes:
> Ethan Henry wrote:
>
> > Perhaps it's time for a JSR for a standard servlet-based template
> > engine?
>
> Does everything under the "Sun" need to be a standard? What's wrong
> with developing multiple solutions based on servlets and letting people
> choose their favorite? JSP, templating, XML/XSL, ECS. All can be
> distributed as Pure Java classes so they'll work everywhere. No need
> for a "one size fits all" solution.
There's nothing wrong with it, but having something bundled as standard does
alot to promote it as standard, which increases the value for everyone else.
Like it or not, there are significant advantages to people speaking the same
language. Better communication, less training costs, etc. Be it programming
languages, or spoken languages.
As soon as something reaches maturity, and becomes a mere commodity, it makes
sense to bundle it with the platform so that everyone can depend on it
being there.
You are lamenting the fact that Sun will, *rightly*, continue to bundle
and promote technologies as they become popular, like Microsoft bundles
disk compression and a TCP/IP stack in Windows. Poor, Trumpet Winsock.
Sun put a lot of widget makers out of business when they bundled Swing.
Pity them. But I'm glad with have a single API, not a dozen APIs when
it comes to widgets.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
