wdym i didn't respond to points you made?
You made the point that:
"some people don't want ScriptAPI bundled" - i acknowledged it
"some form of GUI required and DeepLearning critical" - i didn't object
"Writing everything from scratch is not an effective development strategy" - true, but if the client can't stop crashing you have to strongly consider it.
"AI can't write code" - well it surely migrated bun's entire zig codebase to Rust so it's definitely capable (as of recently AND if used correctly). If you use it right, the output's great. But you can also get the infamous "AI slop" if you don't know how to use it, it's like with googling
I do object to:
"No matter how much you beg for us to remove CEF, I don't care. If you don't like it, don't use it!" - yes, true. but you don't even have to read what i say, you don't have to engage with me.
it's just constructive feedback, not hate, and not begging. i'd love you to take it this way and i'd love to leave a positive impact, but i can't force it on you.
"Also, if you're recommending changing from CEF to another engine, what's the point?" - no engine would of course be best, but if there has to be an engine (perhaps if necessary to properly support the LiquidBounce Design Style, which i also like btw), it might just be a proper one.
flutter comes with near-native speeds on all platforms, no crashes on linux, no forced browser choice, no websocketting between components of the same app, no JIT compilation of a static UI, significant debloating of the client - isn't that long enough to consider a rewrite?
to conclude:
I might try setting an AI to work writing a flutter backend
