Quote:
Originally Posted by kurothelazycat
The code is very much packaged in by default. Just because the "AI" is done through API calls when the setting is enabled does not mean there's nothing built into calibre. There's still all the backend components so that calibre can reach out to those AI options.
Is it wrong to not want this stuff included by default?
|
I don't think it is wrong, but the space footprint looks completely negligible to me (3 Python files for each supported LLM engine as far as I can tell). Assuming there are no calls to this code unless the user really decides to use the functionality, where is the problem?
I personally have no intention to use the feature, and I don't really like the idea either, but I can live with a few more kilobytes on my hard drive.