Comment by Cider9986
4 days ago
I can't use critical software that rejects AI to this degree for privacy reasons.
You can't expect to sufficiently protect your users privacy when not using AI for finding vulnerabilities.
Same thing with Asahi Linux with their highly anti-AI stance. I had a bit of hope when I saw someone was making an LLM assisted fork but it's not the same support.
While MacOS is likely becoming much more secure, Linux distros that reject AI would fall even further behind, if that's possible.
Edit: added critical
Ai and privacy in the same sentence is wierd. You supported your argument, I guess, but unless you are using local ai, the developer would be sacrificing their own privacy.
>the developer would be sacrificing their own privacy
How so?
Something about having a bot controlled by a third party comb your entire codebase and make changes on your behalf strikes me as not the most privacy-friendly approach to software. I know your question wasn't being asked in good faith, but I've answered it honestly.
4 replies →
The current hope is to eventually upstream the “fork” (Gravity) into the Linux kernel. The Asahi project can continue to run in parallel.
The Linux kernel extensively uses AI now; most lkml submissions have an Assisted-by: LLM tag.
The Assisted-by: tag is no longer requirement because LLM assistance is the default.
Robot friends enable you to get much more done faster and more accurately, that if you call yourself an engineer you're a damn fool not to make use of them.
> The Assisted-by: tag is no longer requirement
Do you have a link? Because this contradicts the kernel documentation.
https://docs.kernel.org/process/coding-assistants.html
1 reply →