Django tip: Caching and two-phased template rendering
holovaty.com
holovaty.com
The mechanism we use for this is to do some ruby metaprogramming to kludge in some placeholder values for the uncurried values, and then gsub them in in the subsequent passes. (So, the first pass is the only pass that runs the HAML/ERB file, the rest are gsub's) This works for us, since things after the first pass are not changing layout, etc, and need to be high performance. The first pass is a heavyweight rendering at a coarse granularity (and cached), subsequent curries are lightweight gsubs at fine grain.
I'll take Django, thanks.
But, if I'm not mistaken, Drupal with users is slow because pretty much any function in the system is allowed to change its output depending on the logged in user, right? And that's pretty tricky to cache.