The Problems with JSP, an old article by a Go.com'er, justifies the use of template engines over JSPs. Having worked with Go.com's open-sourced TeaServlet in the workplace, I've seen how well the template engine model works with workflow, especially in a media site situation where templates are produced daily, while applications (and anything that needs app-style functionality) are only created every once in a while to handle special circumstances. I even dislike the way I've written entire apps in PHP, with their design strewn about the app's source code. (Admittedly, I can use different practices and still use PHP, but I'm not likely to break my own, insignificant apps with small, quick changes. And when I do break my own apps, it doesn't cost me money, or cause a dozen people to be paged in the middle of the night.)