News for hackers. Stuff that matters.

A comment on Git 1.7.7 changes affecting the everyday developer. Parent comment

Re:Git 1.7.7 changes affecting the everyday developer by peterjmag on Friday October 14, 2011 @08:37PM (#3113579)
Anyone know why WordPress doesn't ship with some form of caching?
[ Parent | on HN ]
Re:Git 1.7.7 changes affecting the everyday developer by kemayo on Saturday October 15, 2011 @02:16AM (#3114210)
As I understand it, basically two reasons:

1. WordPress is very proud of its quick-setup process, and caching needs to be configured away from the defaults on a non-trivial number of systems.

2. Using caching makes your blog less dynamic. Things like "latest comments" don't update immediately across your site. Users who haven't explicitly installed caching don't necessarily understand why this isn't a bug.

So WordPress makes it really easy to install a caching plugin, and lets the tiny number of blogs that get enough traffic to need it install it themselves.

[ Parent | on HN ]
Re:Git 1.7.7 changes affecting the everyday developer by jacques_chester on Saturday October 15, 2011 @01:59AM (#3114185)
Because that's not the Wordpress Way (tm).
[ Parent | on HN ]