This is probably a bad thing. I'd think that most
of the settings
that fragment the parser cache should be implementable in a
post-processing stage, which should be more than fast enough to run on
parser cache hits as well as misses. But we don't have such a thing.
some of which can be even done with css/js, I guess.
I'm all for simplifying whatever processing backend has to do :-)
Domas