However, lots of people get confused by caching plugins when they're editing templates and things.
Idea: Wordpress caches pages. It checks to see when its template files were last touched. If they were touched after the cache, it regenerates. Otherwise, the cache is served.
You can have that for free, Wordpress.
If I just want to set up a personal blog that I don't plan on promoting or spending a lot of time on I wouldn't want to spend any extra time setting up things that don't help me with my primary goal, writing blog posts.
If you're not using WP, you might use something like Tumblr or Posterous. In that case, caching isn't your problem. If you rolled your own blogging software, well, you already violated the principle that blogging is your primary goal.
It also increases the barrier of entry to posting something, so I'm less likely to post something inadequate.
I find that mentality kinda odd.
Plus, I'd grown lazy from my lack of traffic :)
http://www.viper007bond.com/2010/08/10/why-wordpress-doesnt-...
I don't mean to level criticism solely against the post author for this, because he is not alone, but I find this mentality inexcusable. This is especially true if you're using WordPress, for which there are a multitude of caching plug-ins. All of which will offer orders of magnitude better performance than allowing the blogging engine to build the page from scratch every time.
In other words, caching is always a priority. It's not an add-on or an after-thought, it should be part of your design.
Consider a scenario where someone asks you to add up three arbitrary numbers:
123 + 456 + 789
Now, imagine you type those in to a calculator to add them up. It takes you a few seconds. The output is 1368. You can easily remember this number, so the next time someone asks you what the result of 123 + 456 + 789 is, you can just say 1368. Not caching is like keying the numbers in to a calculator every time, rather than just relying on your memory.
I know this is a rudimentary example, and I know that most people running a WP blog probably know how caching works, but even if you don't "need" it today, why would you leave your blog set up so that it's constantly re-building content that can be cached by simply installing a WP plug-in?
I implore you. Make caching the second thing you do (after security) when setting up or building your web app.