Replying to @jonny@neuromatch.social
@jonny That's the real "red team"; Convincing your boss that AI can do everything, and do it better than you. They adopt it, and then riddle everything with bugs
Replying to @jonny@neuromatch.social
@jonny That's the real "red team"; Convincing your boss that AI can do everything, and do it better than you. They adopt it, and then riddle everything with bugs
Replying to @zm@kolektiva.social
@GrapheneOS
If you're looking for inspiration or feel like people are demanding the impossible, look at @elementary
This is OS development without AI.
Replying to @zm@kolektiva.social
@GrapheneOS
> It's ridiculous to portray experienced developers overhauling the app with everything going through a lot of review as writing slop because one uses AI tools.
To my previous point, even if you feel that they're not writing slop because of AI use. They still are, because of the reputation they have of being used for that purpose (even among the best developers). Historical precedence shows that using AI over time will de-skill and you'll just vibe code eventually
Replying to @GrapheneOS@grapheneos.social
@GrapheneOS
I still think you have to look at what this means from a cultural perspective.
Even if this is all true (i.e. you were getting amazing quality output from LLMs), it doesn't answer for all of the negative externalities of AI use (just look at why Codeberg banned it). You have for the most part called balls and strikes on a lot of the controversy and misconceptions surrounding this project and other similar projects.
It's given you a good enough reputation to get the user base you have and even land you in the news because of how secure it is. AI companies on the other hand have a terrible reputation and many people are jumping ship to something like GrapheneOS because of AI (and how it's being forced on their users)
If you can understand the reasons that people want to use GrapheneOS then you'll understand why people don't want you to allow AI use in this project. None of the technical challenges you're facing will even matter if your users can't trust you
Replying to @GrapheneOS@grapheneos.social
@GrapheneOS
> Creating a Linux distribution not heavily using it would require a hard fork of the Linux kernel and many other projects.
The pitfalls of using LLMs are well known and documented. Hard forking everything would probably be for the best really. Leaning into it, out of pear pressure is really the bad move here (unless you think there's more to it than "pear pressure")