On Jun 6, 2007, at 10:34 AM, Tina Müller wrote:
well, many people say, why optimize code if the database is slow
anyway.
i don't like that. if you can optimize by using a fast module - why
not?
and by the way, JIT doesn't have many features, while HT::Compiled has
the dot syntax.
Well with this sort of system, it makes sense to optimize the code --
either way you're using the same templates. Easy choice.
But simply choosing 'the fastest' templating system isn't always the
best idea -- it can ,and often does, lock you into a templating
system that can be extremely hard to migrate from in the future.
I'm not a fan of disregarding db blocking when you optimize -- you
should always go for the best/fastest possible route.
When i looked at Petal, which was slower than many of the other
engines, the speed difference was rendered negliblle when measured
against the db blocking.
i could have chosen a faster engine, but the speed wouldn't have
mattered much in context, and I wouldn't have the portability that
Petal offered me.
So i went with petal, then optimized elsewhere.
// Jonathan Vanasco
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| CEO/Founder SyndiClick Networks
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
