Now I definitely know you haven’t seen a real professional codebase. Professional git repos are full of one sentence commit messages with little to no explanation of what’s in the change set.
Humans suck at communication, especially when there’s pressure to get product features out the door. AI driven repos are full of beautifully summarized commits with clear explanations of architectural choices, change motivation, etc.
This can easily be resolved with a more direct default prompt. But I actually prefer the verbosity of the standard system prompts. It allows for much better exploration and learning opportunities.
You must not be working professionally.
Fair enough. Don’t you think it simplifies the issue a little bit? How long would it take to rewrite the entire TCP stack in rust?
Clearly, but it’s worth pointing out that this kind of problem isn’t uniquely fixed by “just use Rust”.
So could have Java, Go, C# or any language with GC. With garbage collection, the options object stays alive as long as any CPU holds a pointer to it, so use-after-free can’t happen.
Besides, this exploit is so hard to pull off the only realistic outcome is a kernel panic, and that hasn’t even been publicly demoed.
You reap what you sow. For years I would attempt to contribute to open source projects with minor improvements and bug fixes, leaving well thought out PR descriptions, only to be rejected because of a slight formatting error in my submission or because of the maintainers’ egos.
You want real human connection? Go outside and talk to someone. Open source code is just that–code. And code has always been the realm of computers and technical correctness.