>if you release software people expect of you to update that

a) Don't write shit software that isn't worth updating
b) Don't write shit software that people won't pay you to keep up to date

>>61128325

part of programming is keeping your programs maintained and up to date, especially if you're using databases

dumbass

>>61128377
>>61128413
>be programmer
>release quality software
>people guilt trip you into updating your software
>have less time for new projects

>>61128541

well, i would hope theyre still paying you...

>>61128541
You can hand it over to the well established community of your quality software

Software entropy is a bitch. Just document your code so that someone else can do it if you don't want to keep updating it. You'll probably stay as a consultant though.

Release it as free software and let others update it.

>>61128325
they can fork it, submit a patch, or pay a bounty

Been there. Just release the source or hand it over to someone you trust.

File: you.png (9KB, 454x340px) Image search: [Google]

9KB, 454x340px

>>61128325
Just make sure you write software with a finite scope and no required connection to the internet.
The only problem now is that it stops working with a new OS/platform/minor GTK update. But you can always restrict supported platforms. Or simply ignore it, in case of GTK based software.