Why not render posts at publication time rather than request time?

Wasteful organization.<p>The post:<p><pre><code> http://static.matthewlmcclure.com/s/2012/04/22/wasteful-computation.html </code></pre> One up, 404:<p><pre><code> http://static.matthewlmcclure.com/s/2012/04/22/ </code></pre> One up, 404:<p><pre><code> http://static.matthewlmcclure.com/s/2012/04/ </code></pre> One up, 404:<p><pre><code> http://static.matthewlmcclure.com/s/2012/ </code></pre> One up, something:<p><pre><code> http://static.matthewlmcclure.com/s/ </code></pre> Why do this? I understand the desire to organize, but why make bins with nothing in them? As it is, all he needs is /s/.<p>I would naturally expect .../2012/ to have either all the 2012 posts or all months that have posts, .../2012/04/ to have all of 2012's April posts or all days that have posts, etc. But not nothing.

So we're back to Movable Type circa 2002? ;)

Yeah, we've discussed this before. <a href="http://news.ycombinator.com/item?id=2945463" rel="nofollow">http://news.ycombinator.com/item?id=2945463</a><p>I think the ubiquity and ease of use of things like WordPress causes people to overlook this solution. Also, I believe the caching plugins that people use with WordPress are doing something very similar.<p>There are a lot of static site/blog generators out there like Jekyll, but not many of them are targeted toward a general audience. WordPress is easy and well-known.

Mainly because currently people's time &#62; computation time.<p>Is it even worth my time to setup caching on a blog that gets 10 hits a day? Probably not.

Publication time or request time doesn't matters, Varnish is in front.

Because premature optimization is the root of all evil

Every major blogging framework has caching either built in or as a plugin.