dikini.net

I must admit, I'm doing it too. But why oh why, people thing that they must use an sql server, when writing a web application framework. It is beyond me.

Some will say, "Well my/pg/ms/any sql server is fast, it it there, it is ubiquous, flexible and everyone is doing itr, so you can find books about it.

Let's tackle these pros one by one in our context.

Fast

Indeed, it can be. SQL server software is usually designed to work with vast amounts of data, stored on some secondary storage. Relational data can be organised, searched, extracted fast. Sure. But. There is always one. A web application framework doesn't know the exact nature/model of the data. It usually builds a palette of primitive types, then does some magic to join those types per application type. You'll find object-relational mappings, sql synthesis algorithms, others, whend dealing with this problem.

To continue my random ramblings on the programmable web let's get into the other side. Theming.

These days it is a common place to have a theme engine available in almost any respectable web application. It's the result of the spearation of concerns mantra and the desire to get designers and arty types off your back, give them the freedom to do almost anything they want, while not bothirng yourself (as a developr/admin) with too much unnessesary support requests. Theme engines and ideas how to build them are plenty. They differ a lot. But let's try and dissect what are they doing, or more likely what should they do.