"You are shirking your duties onto others."
That might be true if you had a duty to them. But you don't.
That might be true if you had a duty to them. But you don't.
There has to be a better way. The reason I think the distinction is important. One is a world where we spend more time as developers struggling to keep our balance as the floor constantly moves. And, therefore less time spent on solving actual problems. While the other potential world is one where we create a self-healing structure that somehow makes life easier for both the maintainers and end users.
I honestly don't know how it would work, but I definitely feel it exists somewhere in our future.
I'm not sure you're on the right track by thinking of this in terms of "duty". Someone might be working on open source for any number of reasons, possibly none of which are because they feel a duty towards any particular user of the tools they're working on. They may simply wish to produce the best, most secure tool possible at the lowest cost to themselves. That doesn't mean they have a duty to (say) keep around older, insecure versions just so users who haven't done their own due diligence can minimize work disruptions.
Given the lack of an existing "better way", I'm more than willing to cut open source maintainers a bit of slack until such a time as I'm paying them decent rates.