If I were a dev, that would be the number one reason I would not publish any app I created. The constant demands from users, the constant integrations, et al, nah…pass. I am grateful for who do, but that’s just not my bag.
You can keep running the project and invite people wishing for an XYZ integration to open a pull request. The collaborative nature is kind of a big point of open source imo.
Didn’t downvote ya but, yeah I guess I could do that if I were a dev. Also, I would personally feel responsible for someone’s loss or havoc caused my my app.
If I were a dev, that would be the number one reason I would not publish any app I created. The constant demands from users, the constant integrations, et al, nah…pass. I am grateful for who do, but that’s just not my bag.
He specifically goes on to say it’s primarily from dealing with anti-AI backlash in response to his use of Claude to help (solely) maintain the client: https://github.com/andrewrabert/jellium-desktop/issues/609
One could also not feel obligated to address all requests and just let anyone fork the project.
Isn’t it a bit about the ego to keep running the project while it’s too much to handle?
You can keep running the project and invite people wishing for an XYZ integration to open a pull request. The collaborative nature is kind of a big point of open source imo.
oh absolutely. I only meant in case it’s physically too much for the repo owner.
There’s no need to feel obligated to carry on to one’s own detriment. The community knows how to move on with it, e.g. ownership transfer or a fork.
Didn’t downvote ya but, yeah I guess I could do that if I were a dev. Also, I would personally feel responsible for someone’s loss or havoc caused my my app.
Which is one of the reasons I’ll never implement the delete function in the Jellyfin for Roku client.
Sure, I’m assuming the project has a stable version and a warning or archived banner clearly advertised 😉