3 ms·
Isn't this obvious? We have a really good toolchain for dealing with filesystems. The toolchain for dealing with content in databases is not nearly as good.
by btilly 17y ago
Isn't this obvious? We have a really good toolchain for dealing with filesystems. The toolchain for dealing with content in databases is not nearly as good. As a result static content should be kept in the filesystem, even if you have to play tricks to do it.
The use case for web pages created dynamically out of the database is user generated content. There our existing toolchain doesn't matter because users don't get access to your filesystem so you have to create new tools anyways. And a database makes it easier to keep data structured, takes care of transactional mechanics, and has good tools for things like failing over in event of a machine crash.
Seriously we had a build/compilation step as part of deployment back in the first website I ever worked on. We didn't use a CMS to do it though, we used a homegrown templating system (later changed to Template Toolkit) and a Makefile.