[wp-hackers] Caching as part of the core

[Chason Chaffin]

Why not just install mod_pagespeed on the server?

It keeps coming back to this, WordPress core should not be in the business
of adding features to make people who don't know what they're doing just
get themselves into more trouble. Adding all these features increases
maintenance for the core devs, and adds unneeded complexity and feature
bloat for people who do know what they're doing. Additionally, the results
of Google Page Speed and any other tools like that have more to do with
minification and browser caching which is NOT object or page caching and
has very little do with them. AND they are also misleadingly complex topics
that would be very difficult to find a "standard" setting that would please
everyone or even most people.

If someone doesn't know what they are doing it is far better to suggest to
them to hire someone who does, rather than build extra code into the system
to hold their hand. This is not a usability issue, this is an issue with
complexity. You can't just program away complexity, and caching,
minification, and page optimization is something that should be done by a
professional that knows what they are doing. The reason WordPress has such
an awesome plugin architecture is to allow for extensibility like this.

Here's the documentation on the existing API that came up as the first
result of a google search for "WordPress caching API":
http://codex.wordpress.org/Class_Reference/WP_Object_Cache

The benefits of building a more advanced caching/page optimization system
do not outweigh the costs in the calculus of development.

On Fri, Jul 20, 2012 at 10:14 AM, Almog Baku <almog.baku at gmail.com> wrote:

> And still, by YSlow rate, and by Google PageSpeed rate- the basic WP not
> passing much fields like minification, caching, browser caching and other.
>