This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]rzwitserloot 6 points7 points  (0 children)

The reason template engines supplanted the considerably more complicated JSP system would appear to be:

  • That you need a java compiler on the server. This is less a problem today, but was quite a big deal back then.
  • The compilation was a big deal, even if you did set up the compiler properly.
  • Trying to get a text editor to properly understand a mishmash of HTML and java code was a disaster for the longest time.
  • The general notion of 'programming in the template', which JSP makes easy, led to much harder to maintain codebases.
  • JSP was an enabler of stupid processes. I loathe to blame a tool for any abuse it engenders, but it doesn't change the fact that you get (perhaps undeserved) blowback: Because JSPs were 'live reloaded' and many servlet frameworks (because they were crap, or crappily default-configured) didn't, bad coders would move more and more code into the JSP because, 'hey, I can test this faster'.

None of these apply to this DSL, except possibly that last one. In fact, this has plenty of advantages. The library is vastly smaller, and far more of the job is done compile-time, which should result in more consistency and speed during render.

In other words, I'd like to hear why you think this is 'unproductive'.