True. It should however be noted that the most active maintainer of AnkiDroid will be joining the new entity:

> We’re currently talking to David Allison, a long-time core contributor to AnkiDroid, about working together on exactly these questions. His experience with AnkiDroid’s collaborative development is invaluable, and we’re grateful he’s willing to help us get this right. We’re incredibly excited to have him join us full-time to help propel Anki into the future.

▲

KPGv2 28 minutes ago | parent | next [-]

Yeah, and while they say AnkiDroid is going to be maintained by the original creator separate from AnkiHub, we won't be privy to any employment contract language that makes any work done by the employee as being property of AnkiHub. Which would be an issue.

▲

doctorpangloss 2 hours ago | parent | prev [-]

anki has so much potential and has such a big and unique audience, it is incomprehensible to me how it has managed to be so neglected.

and then now why, of all times, when a solo developer is never more productive, would the lead maintainer cede ownership? the antidote for programming burnout has just been invented, just take it haha

	▲	TheDong 2 hours ago \| parent [-]
		My experience using AI is that it wildly increases burnout, not decreases it. Writing code is fun. Solving interesting problems is fun. Debugging deep problems is fun. Debugging slop code is a painful suffering experience, having to constantly double check that the AI agent didn't just change the unit tests to "return true" and lie to you is tiring, and the feeling that you can't significantly improve the tool burns me out hard. That last one can't be overstated. When I find a weird behavior that looks like a bug in the linux kernel or rustc or such, I find it exhilarating to read code and understand what the bug is, how it got there, and to feel like I can fix it and never see it again. When claude code gives me a "wrong" output for my prompt, I don't feel like there's any possible way I can go and find what part of the Opus 4.5 model resulted in it not being able to give better output. I feel helpless to debug what went wrong when claude code spirals into the deep end. I can add more initial context, add skills, but those are tiny heuristic tweaks around the giant mass of incomprehensible weights and biases that no human understands. The antidote for programming burnout is not to replace all the fun parts of programming with painful probabilistic suffering.