On 12/20/05, Peter Hunt <[EMAIL PROTECTED]> wrote: > - Templating. I cannot stress enough how important it is for TG to > emphasize ONE and ONLY ONE templating language (we don't want another > templating war). I also feel that Cheetah is far superior to Kid in > terms of performance, extensibility, and the ability to process > malformed HTML documents and create non-XML formats such as CSS and > plaintext.
I'm sure Cheetah (only with a compiled namemapper) currently (and likely in the future) outperforms Kid. Kid's performance can, and doubtless will, be improved. I don't think Cheetah is more extensible than Kid. Kid has an exceptional collection of mechanisms for composing templates. Kid can now do plaintext, but it's certainly not as elegant as Cheetah for that. > That said, however, I think TG should stick with Kid, even > if we merge, because applications are already built with it and > changing the templating language at this stage would be a Bad Idea. Agreed. As I alluded earlier in the thread, I *do* plan to have a way to plug in a different template system, but primarily for the purpose of backwards compatibility and easier transition to TurboGears. Kevin
