Dude, relax. I'm not attacking you. I also said that it may not work, but I'd personally try that first. I wouldn't have thought you were a dev if you didn't know how to go back a version, so I explained more than you may have needed, but the point holds - just because you don't think you have weird installs, doesn't mean there are nuances in your configuration that Apple didn't get to test.
We all have the same problem, and have identified a few different solutions, but none works for everyone (mine seems to help the most on this forum - not gloating, just saying it so people know to try it first). That means that the problem isn't consistently driven by the same issue. That further backs up that there are various nuances that Apple (or any company, including the Apple of 10 or 20 years ago) could test.
I've been a die hard Apple user for over 25 years. My first machine was an Apple ][e. One thing I can say is that I've never paid the Apple tax for engineers to do thorough testing. I've paid it for the brilliance of the user experience vs the competition and for design. Do I think more goes wrong today? Yes, but the software and situation is far more complex (e.g. 20 years ago, no WiFi, Bluetooth, iLife, Flash, video chat, etc). That doesn't mean I'm not ****** when it doesn't work (I freaked out when my machine started freezing, and didn't sleep that night because I was so ****** and wondering how I would solve for it without having to do what it seems you're now stuck with of retrograding to 10.6.6), and don't expect more. But, I still understand that it's not as simple as, "It's because of the iDevices."