Absolutely - caching is a staple of performant code. I agree with you that caching can mask other more fundamental problems, but it's a critical component of any performant codebase. "Don't duplicate unnecessary work" is rule #1. The Rails community has that mantra as its foundation in regards to programmer work (DRY is a wonderful principle), but seems to be content to not expect that same principle to apply to libraries.