A saving is still a saving. And this would be used on a live site, not necessarily what you'd be expected to edit and work on during build stages. As part of your workflow you can use 'beautifying' tools to convert the minified CSS/JS/HTML back and forth when you need to make changes, there isn't really an issue.
Here are examples of to such 'beautification' tools:
Dirty Markup: http://www.dirtymarkup.com/ and
CSS Beautify: http://cssbeautify.com/
The only issue with that however, is that it seriously reduces code readability, for such a small tradeoof.
Sorry I didnt spot your comment sooner - The Easter holidays have disrupted my usual email checking routine
It is true that minifying css might one shave off a few kbs from an existing css file but a saving is still a saving
It makes a more noticable difference when all 3 aspects of step 4 are covered together;
1 - use and external css file
2 - merge multiple css files
3 - minify css
If you're using one external stylesheet already, removing all the whitespace from it is not going to make a huge difference on its own though
Lots of useful information here. 4, 5, and 6 were new to me.
One question though. In tip 4 you removed the whitespace in your example CSS. From my understanding the whitespace doesn't affect the performance of the code to any measurable degree. Why do you suggest condensing it the way you do?