@kaduvert This topic is about the Script API, not your opinion on CEF. It's amusing to me that, out of everything, you say that the Script API is something most users probably want. No, they don't want it. They don't want a 50+ MB JAR file just to have the possibility of running a JS script. Most users don't know how to write their own scripts, and as previously explained, the setup process is hideous and not maintainable.
The browser backend (e.g., CEF) and the deep learning engine are both critical to the usability of LiquidBounce. Without a GUI, you cannot perform any actions. Without deep learning, you cannot use any of the AI-powered or upcoming features.
Writing everything from scratch is not an effective development strategy. Real bloat would be writing everything from scratch yourself. Imagine how much more code would be required to write the GUI exactly as it is and how many months of work that would entail, only to end up with something imperfect and unable to be customized to your liking. The same applies to the rotation system. While we managed to develop and train a model that looks realistic to the human eye within a matter of weeks. Other client developers spend months perfecting their rotation system, only to be detected as soon as it becomes public, as anti-cheats use models trained to detect this, while making yet another rotation pattern is a matter of half an hour with LiquidBounce.
