There appears to be a few bad actors in the Lemmy community spreading ragebait for personal gain
In fact, the same mechanisms added at the beginning to catch bad human written code are the exact same that catch bad AI code
- No, the Linux kernel won't use AI to auto approve code for inclusion. And no plans to do so
- The Kernel actually has a huge number of maintainers. As part of the process, all patches are reviewed by a human who provide feedback as part of the process, and patches get bounced back and forth multiple time.
- Patches don't just magically go straight to master. The maintainers generally have their own branches where it goes to, then it goes to staging trees like Linux-Next. It goes through many eyes, and many tests by the end. The idea that AI code is overrunning the kernel is rediculous
- Maintainers also check that the code meets coding guidelines and is written properly, and solves the problem they are trying to solve. Yes, they also ensure the code isn't slop
- LLM's though might be used to identify obvious problems (bugs / coding guideline issues) with the code. These don't generate "slop" just find issues
- The only thing that matters is the human who submitted the code, as they should be checking the code submitted anyway (including LLM generated code).
Writing bad code isn't something new, and isn't unique to LLM's. Coders (and it seems some "journalists") have been writing slop since computers were invented.
The process hasn't gotten less stringent (probably even MORE stringent as there is an additional set of robotic eyes that can also check), and the same mechanisms that were put in place to catch badly written code 10 years ago, are still there now
What I said doesn't indicate that at all. Not sure how many websocket servers you've written, but there is a reason that there are entire test suites to test them
Even worse, there are all kinds of combinations of half finished frames, masking, etc. The data size isn't predictable and you can also have fragmented frames too.
We also need to connect to all kinds of clients which do things slightly different
And, I had limited time to write it in as well.
If you're not getting any bugs, you're either not doing anything new, or you're designing really basic apps that offload the hard work to someone else.
Big shocker, but the performance fixing came down to bit handling of the header.. and yes, that made a huge difference overall. The code wasn't wrong...
We're working with embedded systems limited by RAM and CPU that operates on a single thread for everything, with lots of clients .We don't have the luxury of throwing in a better CPU or just pretending it's an issue. Even simply enabling logging drastically changes the CPU usage
I mean, these are your words.