Yes it's new, yes it's pretty; but as a developer it has one very annoying 'feature'. It is determination to use a cached version of the page your on regardless of the number of times you hit apple+r, the refresh button or ctrl+r (for you windows people).
It seems that they have decided to abandon the lovely built in command that has saved many a developer trying to convince a client the page they are seeing is and old version. That great convenience of knowing that one command will work regardless of the browser they're using and can only super seeded by the tyranny of the network admin is no more.
This one little annoyence wasted a good 20 minutes of time this morning! Personally when I do a command that's known as a force refresh I don't expect or want it to look at the cache; isn't that the point of it? You know, to ignore the cache and pull everything fresh from the site.
In their wisdom they have changed their caching method so now when I'm testing a web page I'm building I have to click on a link to it, or re enter the address manually.. Yes it sounds petty, but that fact no bugger published this fundamental change means many of us developers will be wasting time figuring this out!
Please someone make a firebug for safari and my troubles will be over..