I think the issue is not that people shouldn't decide for themselves but
more a question of advising people on the best use of their time.
Learn JSP and that skill transfers to a dozen or more servlet
engines/application servers. Learn WebMacro and you can design using
WebMacro. In terms of professional development, I would rather know standard
JSP than a little used proprietary solution like WebMacro. Not that learning
either one is going to be particularly hard, just that JSP is going to have
far wider applicability.
It is definitely useful to know that there are solutions other than JSP
available. Knowing when and where to use the alternatives means that a
developer can choose the correct solution more often. In my opinion though,
JSP is almost always going to win out over a non-standard template engine as
the correct solution. Add extensible tag libraries (and eventually standard
tags) to the mix and the outcome is even more heavily weighted towards JSP.
-----Original Message-----
From: Jason Hunter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 26, 2000 1:13 PM
Subject: Re: New article: "The Problems with JSP"
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.
===========================================================================
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
