Jason Hunter wrote:
> David Wall wrote:
>
> > And if you passed the ISP back as an array, it would be more like:
> >
> > <% for ( int i=0; i<isps.length; ++i ) { %>
> > The next name is <%=isps[i].getName()%><br>
> > <% } %>
> >
> > I'll grant none of this meets the simplicity of the webmacro solution,
> > though as a Java programmer I have no problem with it <smile>.
>
> In my opinoin, a graphics artist shouldn't be expected to write this.
>
Of course, we originally expected page developers to understand raw HTML codes as
well, but the creation of a robust tools market made that level of knowledge
irrelevant. The same thing will happen for scripting syntaxes when such tools
become available. An intelligent development tool targeted at JSP will have
graceful ways to enter custom tag elements and their attributes, so the syntax is
totally invisible.
How many development tools do we expect to see targeted at JSP syntax vs. any
other given scripting language? :-)
A couple of other points to ponder, somewhat separate from the "good versus bad
syntax" discussion in Jason's comments:
* If I like the WebMacro syntax, but don't like the implementation (say,
it might be too slow for my particular app), what do I do? I suppose
I can go write my own implementation, but of course I can do that with
the JSP syntax as well. However, with JSP there are already (for 1.0)
and will be (for 1.1+) multiple vendors to select from.
* If I need to hire a developer and I key "WebMacro" and "JSP" keywords
into a resume web site, how many hits am I going to get on each?
If people like WebMacro, go for it ... in this particular case, I'm going to stay
mainstream on the projects I manage.
Craig McClanahan
===========================================================================
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
