Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

At least when I tried it a few years ago, the Windows client was also a crappy Python app that ate CPU and disk for around an hour after every startup.

Why? To detect changes, they were storing a snapshot and comparing everything on disk to the snapshot. Which is madness when Windows has methods that don't require reading every damn byte on the disk - at the least, they could use a filesystem minifilter driver, or the NTFS USN change journal.

As if that wasn't enough, after the startup scan they were using an unreliable method to detect further changes (same one as dotnet's FileSystemWatcher, I forget the name of the underlying Windows API).

And to top it all off, even with only 2 systems sharing the data, there were conflicts all the time that required manual resolution (and I seem to recall Dropbox wasn't very good about surfacing these when they happened). Then there was a data loss incident, I presume due to some kind of conflict snafu - Dropbox only support at the time was a forum, and they were completely uninterested in even acknowledging that there was an issue.

I switched to Seafile after that, and haven't looked back. I honestly don't understand why people would put up with that crap, but given the size of Dropbox they obviously do...



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: