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.
After reading both the accusations and the dev response I don’t know who to believe. I love BookLore and have not encountered any issues, so I guess I’ll stick with it for now.
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.
The BookLore thing is really disappointing. I hope we see a quality fork in the near future.
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.
Good code has always been about simplicity, taste, and understanding.
If a human provides understanding and taste, they can elevate AI code to be good.
Likewise if an AI isn’t well guided it won’t understand, has no taste, and will generate overly complex code. AKA Slop.
Exactly. And a commit is a commit. Unless it’s 10Kloc in one go you can just read what’s in it and decide for yourself.
At my previous job we used to jokingly (?) tell our engineering manager “no commits, no opinions” well I think it’s kinda like that.
After reading both the accusations and the dev response I don’t know who to believe. I love BookLore and have not encountered any issues, so I guess I’ll stick with it for now.
I have seriously considered spinning up Booklore. Great looking UI. Oh well.
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.
They said they were disappointed, not mad.
Just read through some of the BookLore stuff and that was a wild ride.
Yeah… I will not be updating my instance for a while. Will probably start looking for something else.
Wild ride…