That’s a bit harsh. While I understand not wanting to perform a new OS update (at least not immediately) or not being able to (they deprecate old hardware too) I do understand that it’s a matter of resources and that most people are going to be on a handful of your most recent releases, so it makes sense to spend your time on those.
At the same time (most) people don’t actively seek to disable updates for things until something goes wrong. If your app is working on my current OS and filesystem it’s incumbent upon you to recognize that and not automatically push out an update that breaks that.
For something as relatively simple as Dropbox’s original functionality (all files from folder x are synced to their server and every other machine on your account) it also seems like a relatively reasonable ask for them to version things and continue to support that functionality for quite a long time.
> it also seems like a relatively reasonable ask for them to version things and continue to support that functionality for quite a long time.
Or... just don't force an upgrade. Notify me at some point that it might not be 'supported' after a certain date, and subject to data loss, etc. We understand with many other pieces of software that after a certain date, they may still 'work' but we won't get support.
There's certainly some security risks to deal with there, and perhaps reminders closer to cutoff dates would help?
But, yes, basically agreed.
relatedly, I've had dropbox on and off, but felt pushed in to paying for it, and resented that push (and ultimately never did). Had multiple client years ago all 'love' dropbox and wanted to work that way. They all loved that it was 'free', but... when I had to work with 5 of them, each sharing up to their 'free' limit with me, it put me over the free limit in to 'pay up' territory. Not a 'break the bank' amount, of course, but it bugged me that I needed to fork out.
> Or... just don't force an upgrade. Notify me at some point that it might not be 'supported' after a certain date, and subject to data loss, etc. We understand with many other pieces of software that after a certain date, they may still 'work' but we won't get support.
> There's certainly some security risks to deal with there, and perhaps reminders closer to cutoff dates would help?
That was actually my whole point. If you have security updates to push, then push them. An automatic push should not break my existing functionality under normal circumstances. There will always be extraordinary situations where it’s required, and at some point you do have to make the tough call that the hundred people still using something will just have to deal with it... but it shouldn’t be the norm.
At the same time (most) people don’t actively seek to disable updates for things until something goes wrong. If your app is working on my current OS and filesystem it’s incumbent upon you to recognize that and not automatically push out an update that breaks that.
For something as relatively simple as Dropbox’s original functionality (all files from folder x are synced to their server and every other machine on your account) it also seems like a relatively reasonable ask for them to version things and continue to support that functionality for quite a long time.