Artemis was a promising mobile app for Kbin, with a dedicated community, a rapid pace of development, and a high level of polish. Then, the developer disappeared.

you are viewing a single comment's thread
view the rest of the comments

[–] Bishma@discuss.tchncs.de 103 points 11 months ago (4 children)

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.

[–] partial_accumen@lemmy.world 61 points 11 months ago (2 children)

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 26 points 11 months ago* (last edited 11 months ago) (3 children)

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. It's a problem.

[–] partial_accumen@lemmy.world 18 points 11 months ago

It’s a problem.

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 6 points 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 5 points 11 months ago (1 children)

Yes, but if you’re lucky maybe 1 in 100,000 users will be both capable and willing to take up the reins

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 points 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.

[–] ____@infosec.pub 7 points 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.

[–] ipkpjersi@lemmy.ml 10 points 11 months ago* (last edited 11 months ago)

That's why I open-source everything I work on, or at least, everything I have permission to. I have one or two projects where I have friends who have contributed a good amount of code but don't want it public so I respect their wishes and keep it private. Everything else I work on though, it's open-source.

If I can't or won't continue working on something, maybe someone else can find it useful and continue working on it.

[–] Fitik@fedia.io 4 points 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

[–] onlinepersona@programming.dev 4 points 11 months ago

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