I'm considering writing an alternative Dropbox client for Windows, because the official client seems to have a couple of major (for me) issues that don't seem to be going away any time soon:
- Indexing on startup is very slow (~4 hours for 85K files), during which time the machine is almost unusable due to both the CPU and disk being thrashed (on an i5-3570k)
- Functionality is basic; everything must be stored in a single folder, and you can't exclude files using patterns (e.g. *.bak, *.lrprev etc)
But I just read that API calls are rate limited, which may well mean that it's just not practical to have an alternative client, because performance would be so poor.
I realise you don't publish figures for the rate limiting, but before I spend any time on this it would be good to know whether the rate limit is likely to be an issue or not?
