Timbalu wrote:In other more extended cases, this just blows up that file. Then a secondary css file added to head (or wherever) is good enough too.
We can not measure if that's the case, though. We do not know if any given blog uses one plugin that references one extra stylesheet or five plugins with seven stylesheets altogether. We also do not know if the theme any given blog uses maybe already references a second stylesheet because it uses Google fonts.
What we do
know is that if we push all the stylesheet assets to serendipity.css, the core will generate one
stylesheet reference. I feel that approach is always better than not knowing, but I can respect that other people have different opinions.
Timbalu wrote:the serendipity.css file, which then changes very often
Why would that change “very often”? It changes if any of the components that push to it change something in their styles, does it not?
About the only
argument that I see is plugins that use external libs (like lightbox, which ironically is how I even came to think about this). If it is not feasible to push the stylesheet files provided by those libs to serendipity.css, I can accept that because it would be a pain to maintain otherwise.
Timbalu wrote:It would be nice to clear that by example and still have the choice to do it in either way by preference.
I actually think the best
solution would be to find a way to leave that up to the people who actually do
judge – the users. That would mean to have a plugin option for it – reference plugin stylesheet seperately or push it to dynamic stylesheet. That
would actually be great IMO.