Whoa, activity on trac-dev! :) > I agree that adoption of Jinja2 should be considered, it's become a very > solid templating solution, and comes with both more momentum and better > performance than Genshi.
It's already a good sign that nobody has anything *bad* to say about Jinja2. Still, is this the only reasonable alternative? Are there other contenders out there, and what are the pros and cons of each solution? I'm not trying to work against Jinja2, just to keep the view broad before making a choice. > But I'm not sure how a gradual transition could work. (snip) > If there's going to be another template engine switch, I think it's going > to hurt. But it might just be worth it. I'm a bit wary of how this could work out. Let's say (for the sake of argument) that we switch to Jinja for 0.13. This is a large internal change, but mostly invisible to end-users (except for better speed, which may or may not have a significant impact). Besides, we either break most of the existing plugins (if we don't transition gradually) or increase the work significantly (if we transition gradually). So, we get a new release where: - a big chunk of work is barely visible to end-users - plugins stop working for no (user-understandable) reason - themes and style customizations stop working I do hope that if we go this way (and maybe a radical but painful switch with limited backward compatibility is the best solution), we can at least bundle it with a few highly visible, high value features. Improving internals is all well and good, but at the end of the day, it's the user-visible features that the users care about. -- Remy
signature.asc
Description: OpenPGP digital signature
