With regards to point number 1, I don't understand how that bug could have existed uncaught. Yes, security is hard but when you're storing the most personal user data, you're obliged to make sure you actually keep it safe and protect it from unauthorized access.
Yet, with Dropbox, it appears that every so often that some time goes by, and we have yet another security issue. The worst I remember was when for a window of time, _anyone_ could login to _any_ dropbox user account without entering a valid password. No password. Just a valid username and you're in.
It's interesting to note that issue too had to do with authentication and authorization. Maybe it's time Dropbox should spend some time auditing their code to find other similar issues just waiting to be discovered?
As you pointed out, dropbox has shown they're not very secure. They lied about their server-side encryption too. But no one cares. It's far more profitable to make a reasonable pass at security, then try to deliver on the user experience and marketing.
Everyone I know in a security-conscious environment uses something else. Sadly, often MS Sharepoint. There are some big advantages to a system like Dropbox, but aside from some small startups, nothing in that space I'd actually recommend for business use.
(1) Dropbox is inconsistent about whether it ignores dots in the local part of an email address, and in some cases blurs the line between accounts with similar emails. If true, this needs to be fixed.
and
(2) Dropbox doesn't really use two-factor authentication, in the usual sense of "something you know plus something you have." I'm guessing this is due to their users liking the idea of having two-factor authentication, but in practice want to be able to access their account even if their phone is lost. So it turns into "something you know plus something you know." I'm inclined to think that this kind of not-really-two-factor-authentication is actually the correct approach for the kind of data you store on Dropbox, but it's something to think about when you're designing an account-recovery protocol.