What is the difference between Tea vs. WebMacro?
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. Tea is compiled to Java byte code and runs in the JVM. WebMacro runs in an interpreter and is slower than Tea. In addition, WebMacro accesses properties from objects using reflection calls, which can have an initial overhead 10 to 100 times slower than ordinary method calls because they can’t be inlined. Although WebMacro caches the result of introspecting beans, it cannot fully eliminate this runtime overhead.
