Hi Andreas, There is one thing I miss when writing a ESP: lack of IDE integration. Anyway, the JSP integration is normally not perfect when writing a Sling application, specially because some implicitly defined objects [1], which the IDE is normally not aware. But I'm also biased, and I normally favor JSP over ESP. :-)
Regards, Douglas [1] http://cwiki.apache.org/SLING/scripting-variables.html On Tue, Mar 10, 2009 at 09:21, Bertrand Delacretaz <[email protected]>wrote: > Hi Andreas, > > On Mon, Mar 9, 2009 at 8:58 PM, Andreas Hartmann <[email protected]> > wrote: > > from your experience – is there any significant difference between the > > scripting languages?... > > Here's my personal opinion, comparing ESP to JSP, YMMV ;-) > I'm biased, as a big fan of server-side javascript. > > > * Readability, verbosity > I much prefer ESP over JSP: used well, the dynamic aspects of the > language help a lot. > > > * Modularization of pages > No difference IMHO. > > > * Access to Java API > Very similar, though some catches with ESP. for example when rhino > cannot choose between overloaded methods due to type ambiguity. > > > * Support by Sling (feature completeness, bugs, …) > I think support is equally good. > The ESP debugging tools could be improved though - in general JSP > tooling is often better or easier to find. > > > Or is it just a matter of personal taste? > I think it mostly boils down to personal taste in the end. > > Though I prefer javascript, well-written JSP is good, but I've seen > lots of crappy JSP in the field, probably because it is too easy to > use JSP without being aware of issues like separation of concerns and > readability. > > -Bertrand > -- Douglas Jose http://douglasjose.com - "Use free software. Help us make a free world."
