I think it's more important to know _when_ the downtime occurs vs. the percentage itself.
If the site is down from 12am to 6am due to some botched maintenance, I really don't care, as traffic will be minuscule, if not non-existent for our core market. And 6 hours of downtime is a killer for uptime percentage.
The "Jekyll is so easy! It's the easiest thing I've ever maintained!" argument reminds me of Andy Rubin's now infamous quote about the openness of Android: "the definition of open: "mkdir android ; cd android ; repo init -u it://android.git.kernel.org/platform/manifest.git ; repo sync ; make"
The point of Tumblr is I don't need to maintain _anything_!
If the site is down from 12am to 6am due to some botched maintenance, I really don't care, as traffic will be minuscule, if not non-existent for our core market. And 6 hours of downtime is a killer for uptime percentage.
The "Jekyll is so easy! It's the easiest thing I've ever maintained!" argument reminds me of Andy Rubin's now infamous quote about the openness of Android: "the definition of open: "mkdir android ; cd android ; repo init -u it://android.git.kernel.org/platform/manifest.git ; repo sync ; make"
The point of Tumblr is I don't need to maintain _anything_!