I'm not enjoying the future where we pick between unmaintained but no AI fork or maintained but Claude was here repo
-
I'm not enjoying the future where we pick between unmaintained but no AI fork or maintained but Claude was here repo
because, being real here, these sorts of forks are going to be abandoned irrespective of how noble your intentions are, solely because the people doing the forks are often not the people who had an interest in contributing before
you are not going to develop an interest in contributing to a codebase just because upstream started using genAI
-
I'm not enjoying the future where we pick between unmaintained but no AI fork or maintained but Claude was here repo
there's also the occasional gem that needs no fork as they have a no-ai policy, eg snac put that in their guidelines just today
-
@theresnotime@fox.nexus i was bitching about this just this morning . "pre ai fork" bro if i wanted to pin to a specific commit i can do that myself , thats what git is for
@fiore @theresnotime the biggest problem ive got is like... objectively this does probably maybe void the license meaning packaging versions of vim past that commit is uh... legally dubious and may be avoided by some distros -
because, being real here, these sorts of forks are going to be abandoned irrespective of how noble your intentions are, solely because the people doing the forks are often not the people who had an interest in contributing before
you are not going to develop an interest in contributing to a codebase just because upstream started using genAI
@theresnotime Real tbh. Because by the aims of the fork, they won't take upstream patches like many of the successful βX but without Yβ forks have in the past (see Firefox and Chrome forks).
Unless they're able to sway existing contributors over or are willing to step up and dedicate real effort to working on the project, the capability and bug drift will get real very quickly (not to mention security patch drift).
-
@fiore @theresnotime the biggest problem ive got is like... objectively this does probably maybe void the license meaning packaging versions of vim past that commit is uh... legally dubious and may be avoided by some distros
@coolbean @theresnotime@fox.nexus vims license isnt voidrd you just have to include it and tell people to sejd money to uganda or smth
-
@coolbean @theresnotime@fox.nexus vims license isnt voidrd you just have to include it and tell people to sejd money to uganda or smth
@fiore @coolbean @theresnotime every license should require this tbh
-
@coolbean @theresnotime@fox.nexus vims license isnt voidrd you just have to include it and tell people to sejd money to uganda or smth
the old vim maintainer who was championing for that died, iirc the notice got removed from vim and the charity got disbanded bcs he was actually the only reason they still existed. or smth like that, i remember seeing a post like "if you still wanna send money, send to this other charity in usa instead"
CC: @coolbean@brain.worm.pink @theresnotime@fox.nexus
-
the old vim maintainer who was championing for that died, iirc the notice got removed from vim and the charity got disbanded bcs he was actually the only reason they still existed. or smth like that, i remember seeing a post like "if you still wanna send money, send to this other charity in usa instead"
CC: @coolbean@brain.worm.pink @theresnotime@fox.nexus@eris @fiore @theresnotime i use nvi Version 1.79 (10/23/96) The CSRG, University of California, Berkeley. -
@eris @fiore @theresnotime i use nvi Version 1.79 (10/23/96) The CSRG, University of California, Berkeley.@eris @fiore @theresnotime im immune to ai slop because my text editor hasnt been updated in 30 years
-
I'm not enjoying the future where we pick between unmaintained but no AI fork or maintained but Claude was here repo
@theresnotime loading github code into work projects, while checking the repo is pre-AI but not too old
