I have been using RapidFormatter for two years - so I tend to forget what irritants RapidFormatter erradicates from new WordPress installations:

• When I first started creating themes, I used to update the stylesheet, and upload it to my server, refresh the browser …. and see no change. This used to drive me nuts, as the server cache or my browser cache was using the old version of the stylesheet. It was one of the primary reasons for seeking a solution to edit a theme format that gave much better response times, and also avoided this irritating cache issue.I have been doing some ‘quick and dirty’ quick updates to the site recently - and that damn cache is really proving to be irritating. If the format of the stylesheet looks OK in RapidForamtter, I just trust that the uploaded stylesheet will kick in within a short space of time - rather than trying to force a refresh. My server is particularly stubborn - refreshes from 2 PCs and 3 browsers fails to get it to release it’s greedy grasp of my stylesheet. Even deleting the style.css on the server fails to get it to respond. So - every now and then one of the primary reasons for creating RapidFormatter rears it’s ugly head to prompt me to keep evolving this product.
• Another minor, but always irritating issue that arises with most new installations is getting this sort of message:
  

  About a year ago I built in a process to the theme FTP process so that RapidFormatter automatically uploads an empty .htaccess and sitemap file, and then sets the file permissions. Prior to that I used to get frequent support tickets about this issue. I’ve never had a customer support ticket since implementing the feature. So - by doing the WordPress 2.5 in a step-by-step manner - I bypassed the automatic file upload feature of RapidFormatter - and guess what - the old irritating issue reemerged. Simple enough to log onto the server and set the permissions using FileZilla, but it once again made me appreciate an often-overlooked feature of RapidFormatter.