Seems that Tea and JSP are very similar. Both have the goal of separating presentation from business logic. I need to cycle through a collection that may vary in number each time.
Tea runs through a compiler that has a strict type-checking phase.
With WebMacro, a hashtable is supplied to the template. It cannot be determined until runtime if a property is misspelled or the wrong one is requested. This makes debugging templates more difficult. In Tea, these errors are reported at compile time. WebMacro runs in an interpreter and is slower than Tea.