I’d rather have a happy and productive maintainer than a burnout and an orphaned project. Either way forks can be made at any point - so if you don’t like the use of AI just fork it or don’t update any more and stay happy. No need to get mad at each other.
It’s not radioactive waste, it’s code. You can read it, write it, change it. Just like any legacy codebase it’s full of shit, and maintaining means addressing the specific issues.
This whole debacle is showing that people fundamentally misunderstand how code works. They are trying to declare code good or code bad because of some silly heuristics like ai/not-ai, as if it wasn’t literal lines of text which you can read before you form an opinion and make a fool of yourself.
The BookLore thing is really disappointing. I hope we see a quality fork in the near future.
I’d rather have a happy and productive maintainer than a burnout and an orphaned project. Either way forks can be made at any point - so if you don’t like the use of AI just fork it or don’t update any more and stay happy. No need to get mad at each other.
I’m not sure a fork makes sense given the dev merged way too much nonsense already. Maybe from a point in time before it started?
I’ve been looking to check out Booklore over some annoyances I have with CWA but IDK anymore.
Don’t let perfect stop you from achieving good.
It’s not radioactive waste, it’s code. You can read it, write it, change it. Just like any legacy codebase it’s full of shit, and maintaining means addressing the specific issues.
This whole debacle is showing that people fundamentally misunderstand how code works. They are trying to declare code good or code bad because of some silly heuristics like ai/not-ai, as if it wasn’t literal lines of text which you can read before you form an opinion and make a fool of yourself.