Yes and No. Read the comments I made on the pervious comment, the same arguments almost directly apply to this.
In short, caching using another box is really great for raw speed -- arguably the best solution if that is what you need. However, most people simply don't need this much speed, and keeping the ease/flexibility that the filters I presented offer is arguably the best general solution.
Consider also that the code I presented doesn't by default hurt your ability to scale later. These two filters are transparent to the web app. What do you lose by using them until you need to have a dedicated box for caching, and then how tough is it to turn these filters off and turn your cache box on?