Post #3219962

2026-06-03 12:54 UTC

@whitequark@social.treehouse.systems My nuanced position is that quitting accomplishes precisely nothing because the lack of manpower isn't going to magically resolve itself, and if you think comparing throwing Claude at a **test suite** to modernize it to what Bun did with the Rust rewrite is reasonable, you need a serious reality check. If you don't like the guy resorting to LLMs to handle the deluge of LLM-generated CVEs, go help him yourself. I'll wait.

Replies (7)

@whitequark@social.treehouse.systems 2026-06-03 12:56

@lina@vt.social I am not interested in being treated this way by some has-been who has done precisely fuck all to prepare us for the post-AI era when I've spent my time on barely anything else for a year now

Open ##3219963
@defuneste@fosstodon.org 2026-06-03 13:00

@lina@vt.social I think your are displaying the same behavior you are criticizing. side note: pressure on AI is crazy that is the whole point. @whitequark@social.treehouse.systems

Open ##3219975
@sabik@rants.au 2026-06-03 13:32

@lina@vt.social @whitequark@social.treehouse.systems Rewriting the test suite has nothing to do with handling CVEs

Open ##3219976
@clarfonthey@toot.cat 2026-06-03 14:30

@lina@vt.social @whitequark@social.treehouse.systems 🟧 gonna be honest, this is a pretty frustrating take because you of all people should know better. helping people out takes effort, people will not just merge your patches even if you give them everything they need to do so, etc. this kinda just falls under the usual "why don't you do the work then" argument that has been thoroughly debunked before this is a shit situation for the maintainer, and there is definitely a lot of poorly thought out criticism of him, but this argument does nothing to fix that ultimately, if someone chooses Claude over asking for help and then still doesn't ask for help after the fact, it seems more likely that they are not going to ask for help. so, the choices are either quit or double down and rely fully on these tools, and I agree quitting and letting a community fork take over is the better option

Open ##3219988
@mirabilos@toot.mirbsd.org 2026-06-03 16:03

@whitequark@social.treehouse.systems @lina@vt.social people are working on takeovers of the pre-slop version. I will not say more until they decide to go public themselves. Tridge not only has made himself redundant but a laughingstock and must just quit. (In that Medium post.)

Open ##3219989
@laund@wetdry.world 2026-06-03 18:49

@lina@vt.social @whitequark@social.treehouse.systems it accomplishes something very important: drawing actual attention to the lack of manpower, from those relying on the software, in a capacity which is more likely to find someone to take it over of course not quitting and disappearing, but quitting, perhaps temporarily archiving the repo, and being reachable for vetting someone to take over.

Open ##3219995
@petererer@fuzzle.me.uk 2026-06-04 05:57

@lina@vt.social @whitequark@social.treehouse.systems If you need assistance, then you should solicit that before contaminating your source with LLM-generared code. After that is too late. When the developer then doubles down on using AI, meaning here's no chance of referring the contamination, it's no surprise that people no longer want to assist.

Open ##3219996