[geeklog-devtalk] Optimizing MySQL (was: SPAM Article)

[Vincent Furia]

Actually Geeklog doesn't have horrible abstraction for its template
API. It just that the template API is so old it doesn't really match
up with modern "compiling" template systems.  I know someone tried to
rip out the current template system and put smarty in, but it turned
out to be to big a job.  I think its possible, I just don't think the
performance benefit will be worth the effort (which is substantial).

-Vinny


On Fri, 4 Mar 2005 19:16:59 -0000, Michael Jervis <mike at fuckingbrit.com> wrote:

> > I'd argue that no amount of abstraction here will make

> > changing the template engine easy in 1.3.x.  The adapter

> > simply gives you the clean seperation.  You'd still have a

> > sh*tload of code to change/write if you added support for

> > another templates engine.

> 

> My point was rather that at the design stage you don't /have/ to be

> constrained forever to one theme engine, if you take one of two (or more)

> options. Geeklog didn't so is, but that doesn't mean /all/ systems are.

> 

> Shame, but then you can't always forsee the future, or I'd be the worlds

> first multi-multi-lottery winner. In fact. You can never see the future, or

> I'd at least have matched 5 balls and the bonus by now, rather than never

> winning even £10...

> 

> 

>