You seem to be getting jumped on a bit for this and I'd say it's largely a matter of preference so a little pointless to go on at length about.
However, you are inviting comment by saying "bloat and that is all the stuff that makes code pretty and "easily readable" by inexperienced programmers does." since Python itself is based on indentation (formatting) and can hardly be called a bloated language nor one for inexperienced programmers.
Also the other big point is a stylesheet file is cached on the first page load whereas individual pages and images are often reloaded so arguing about the 7k saved in the CSS file while leaving 1k on every image (I certainly see far more sites with poorly optimised images that could speed things up no end) would be getting "one's" priorities wrong (not saying you do that just a general point).
So in summary it depends where you need to trim. In your workflow you have things narrowed to the degree that you can afford to go to this length but for others this may actually "bloat" their workflow. Part of standards development I'm sure we all love is the improvement in workflow.
Nick
I happen to be one of "those people" and I can say that the practice is
under utilized by the programming industry as a whole. And I am neither anal
nor ANAL, it is simply the method of coding I like to use once I have a page
developed to a point I no I will only be touching it up here and there.
As I stated previously, I look at it as building a rocket to go to the moon
- you want light but solid and reliable. I HATE bloat and that is all the
stuff that makes code pretty and "easily readable" by inexperienced
programmers does.
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
