Of course people tend to not like my UX ideas so its probably a fear I don’t need to have.
Same 😂 My UIs can cause blind rage
Comment on After Radio Silence, Kbin App Artemis Shuts Down
Bishma@discuss.tchncs.de 11 months ago
This is why I never build any of my app ideas. I don’t want people to notice when I wake up one day and decide I don’t want to work on it anymore. Of course people tend to not like my UX ideas so its probably a fear I don’t need to have.
onlinepersona@programming.dev 11 months ago
Fitik@fedia.io 11 months ago
If your project open source then you can do it, and give it to maintainers or someone else, or let anyone work it. Life can get busy for everyone
partial_accumen@lemmy.world 11 months ago
I thought this was one of the points of open source.
“Yeah, I’m done with this. I’m not making any more changes from what it is today. If you find value in continuing it, here’s the code. Go wild!”
Bishma@discuss.tchncs.de 11 months ago
Yes, but if you’re lucky maybe 1 in 100,000 users will be both capable and willing to take up the reins. More often than not, when single (principal) developer projects lose its single developer the project just goes into code rot. ASF “maintains” tons of projects that are too valuable to lose completely but which have no one doing active development on them. Its a problem.
partial_accumen@lemmy.world 11 months ago
Its a DIFFERENT problem.
OP is talking about never creating because of fear of maintaining. How many good ideas have never come to anything because of this idea?
Anafroj@sh.itjust.works 11 months ago
This. Nothing is more difficult than understanding someone’s else code and architecture, and even if you manage that, you’re now stucked with the choices somebody else made and nobody wants that (we want to make our terrible choices!).
More than a final app, the best thing to publish as FOSS is libraries extracted from it to help other developers build there own products faster. That’s something other may want to maintain when we abandon it. And on top of that, it still help to publish your app using this lib to serve as practical example about how to use your it, of course.
Carighan@lemmy.world 11 months ago
So? You as the original developer actively wanted to get away from it, don’t care what happens to it afterwards.
Bishma@discuss.tchncs.de 11 months ago
I’ve never not cared about my code. And If I didn’t care about users depending on it I’d feel like a monster.
density@kbin.social 11 months ago
Not sure what ASF is (something Software Foundation?) but sounds like they are a solution and not a problem
Bishma@discuss.tchncs.de 11 months ago
Apache. The problem is there is foundational software in the world that is aging and not being actively maintained. Basically they jump into action when someone catches a security issue, but also that way too many of those security issues only get found when they’re being actively exploited. Even if it’s being used by your bank.
____@infosec.pub 11 months ago
I can think of only one concrete example where the lead dev walked away - rightfully IIRC - and the community was able to pick it up, fork it, and actually maintain and continue to develop new features.
Sadly, that’s not often the case.
density@kbin.social 11 months ago
I think youtube-dl had a situation like that, now yt-dlp. (except I don't know if the original dev's status is confirmed?)
also exa, now forked to eza. My impression is for this case, the original dev is OK.
But honestly I have encountered lots of software packages which have been dropped and picked up in this way. Man pages can contain history like this, occasionally going back to the 80s or even 70s for the basics. The main problem is that the original software package is so well known and sometimes it's hard to find out about the newer iterations so they have a difficult time picking up steam. I used to have a bookmarklet that would show forks on github sorted by activity; occasionally this allowed finding the more recently-developed project. But more likely you have to wait to stumble on it in a forum.