LLM Usage Policy isn't being adhered to

(#1448) Feature Declined meta

Thread

Comment by @Speykious
RexSystem 1 vote originally by @Speykious on GitHub
Hi, I'm a dev who writes code by hand and contributes to Fluxer. See https://github.com/fluxerapp/fluxer/pull/1129 ? It had 20k added lines of code in about 2 weeks of intermittent work, and that's me not working full time with some significant amount of time spent reading the codebase I wasn't familiar with. That diff is almost twice as big as my immediate-mode Rust GUI framework that I wrote over the course of more than a year. Turns out, Fluxer's codebase architecture just leads to big diffs, is all. I think that instead of just looking at the number of lines of code added, you should take into consideration the amount of these lines that come from generated files. Notably, all of the locales, which use a file format that points back to places in the source code and therefore are susceptible to any source code changes, and the massive OpenAPI JSON files, to cite the biggest culprits. I'd also note that GitHub seems to use a weird diff algorithm. When Hampus started committing to the repo again a few months ago, there was one huge commit that showed 10 million lines of code added, yet when cloning the repo and looking at that commit locally, it was only 3 million, and 2/3rds of that were from automatically generated files. (I analyzed that whole commit back then.) I'm not saying Hampus isn't currently using LLMs to generate anything (in fact first time translations are generated with AI and that's disclosed in the application), only that you can't just look at the number of lines of code on GitHub and judge based on that.