The goals for the projects are different.
The goal of speed is to simplify templates as much as possible to help maintain the separation between logic and presentation, so you donβt slide along the slippery slope of sticking code in templates. This is sometimes correct. Of course, sometimes being able to connect complex logic directly to templates is correct.
Speed ββoften does not change, but this does not mean that it is not in active development. The user community is large, the code is fast and stable, the syntax is mostly fixed. Over the past few years, Freemarker has undergone a rollback in the template syntax and api side. Sometimes it's nice to leave one alone. Again, depends on what you are looking for.
The Freemarker documentation is much wider - and this is a much more complex piece of software.
Many of the Freemarker use cases come down to the desire for a complex template workflow and do not require a compilation step. In recent years, instead of struggling with this with Java, I just used Python or Ruby.
jrb Dec 31 '09 at 7:58 2009-12-31 07:58
source share