Static sites are ridiculously fast because pages don’t have to be generated on load — they’re cached by design. DigitalOcean’s SSD servers help a lot, too. In shared and virtual hosting, hard drives’ RAM caches are unlikely to have your site’s files when people visit.
They’re much more secure because servers like Apache are mature. Because the CMS doesn’t run on the server, I don’t have to worry about appvulnerabilities ruining all the fun.
My site can handle more traffic using the same resources. (This is unlikely to be a problem. Update:It was.)
I didn’t feel like writing a controller script to teach Grandpa Melton’s Magneto how to run a blog, so I used Jekyll instead. Jekyll is also very widely used, making it easier to find solutions for common problems.
Migrating from Tumblr
I’ve had a blog on Tumblr for awhile, but I never really liked the service. It was hard to customize templates and images got compressed to almost nothing. Plus, they don’t offer a mass exporter, which made me nervous about putting a bunch of content there.
Since I only had 11 posts, I just opened the edit view for each of them and downloaded the Markdown source manually and pasted them into Jekyll. I’d kept the original images on my local machine, already organized by post in case I ever needed to escape Tumblr.
We’re going full RMS here
The result of this? All the data needed to regenerate my site resides on drives in my control. And the site is generated and served using open-source tools running on open-source operating systems (running on opaque firmware, but let’s just ignore that bit). Thirty years from now, if I want to, I can fire up a virtual machine of Ubuntu 12.04, regenerate my site, and view it just as it is now. That’s pretty damn awesome.