I'm with Linus Torvalds and GrapheneOS on this. AI is a useful tool, for all its flaws and negative externalities.
this post was submitted on 10 Sep 2026
278 points (90.6% liked)
Technology
88303 readers
2936 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
I am sure I will be down voted on Lemmy for this but using AI for development by a team who is already experienced in development of the product they are working on is not a moral failing.
load more comments
(15 replies)
The crux of that article is buying into Heidegger‘a definition of a tool, specifically, “thing that lets you do something you wouldn't otherwise have been able to.” If you disagree with that premise, the article doesn’t hold up.
Tools aren’t about letting you do something you would otherwise not have been able to do, they are simply a force multiplier for capability or efficiency. You still need knowledge and skills to do the thing.
I am not a carpenter. My knowledge and skills are near zero. This multiplied by any number is still damn near zero, and I have no idea about the culture, safety, or history of carpentry. I’m not stupid enough to jump right into using an lathe without a lot of research or someone to guide me, because I’m not a fucking moron.
People with programming knowledge and skills using AI will eventually figure out a workflow that works. Laypeople using AI to vibe code? They’re probably fucking morons. Sure, maybe even most of the time, it will be fine. But eventually, someone is going to be degloved.
load more comments
(1 replies)
load more comments
(1 replies)
AI is a useful tool, for all its flaws and negative externalities.
"If you ignore the negatives for everyone else and just focus on the positives for me, it's pretty great"
Mhmm. Right, ok.
load more comments
(1 replies)
you know what also was a useful tool? chlorofluorocarbon
load more comments
(40 replies)
I haven't dug into the code, but blanket hate for AI in code is extremely frustrating. There's a difference between vibe coding and the hundred other ways to "use AI" on a project.
It's funny because anyone seeing this as black and white clearly hasn't ever opened an IDE.
I've been a programmer for two thirds of my life up to this point. I don't see how the machine that generates code that must be assumed to be broken, and statements about said code that must be assumed to be wrong, until both have been manually verified, because the "hallucination" issue is inherent to the design of LLMs and cannot be solved, is supposed to make my life easier. Especially since a well known problem in computer science is that writing code is more fun than reading it.
If you're using AI for code generation, I hope you like reading code.
If you're using AI to learn your way around an existing codebase, I hope you're prepared to fact check everything it tells you.
If you're using AI for code review before merging a PR, fucking yikes. What made you think the sycophant machine that once told users a soggy cereal bar was a great business opportunity and cannot even transcribe McDonald's orders correctly was suitable for that purpose?
If you're telling yourself it's okay because there's a human in the loop, please read some studies about attention fatigue and consider that increasing the number of critical decisions a person must make per day, while giving them a suggested answer that's right 90% of the time and catastrophically wrong the remaining 10%, and the only way to tell the difference is to read in depth, might not have the desired effect. Especially if the human in question is then put under time pressure.
And all that is before I go on a five paragraph rant about the ethical transgressions of every major AI company.
It's pretty black and white for me.
load more comments
(14 replies)
load more comments
(10 replies)
I understand this but, you have to consider the ecological impact of it, the thousands or more people whose work was stealed to train AI, the constant shoving of AI into everything and the problems that have arise from it, the campain AI companies did and do telling people they are going to lose their jobs and constant fearmongering, the constant blatantly lying of "AGI achieved", the layoffs by senile CEOs, the debt that is causing because stupid people in power gonna be stupid, etc. There are plenty of reasons to hate AI and what it is doing to our world and people lives in general. Sure there are positives but the negatives clearly outweighs the positives.
load more comments
(4 replies)
load more comments
(10 replies)
I am not a coder in any fashion but this is the make or break frontier for development, particularly FOSS and small scale projects.
AI is evil.
It is an ecological nightmare, socially and economically distructive, prompted on the theft of the knowledge and work of every creative endeavour any person as ever made and pointed at rendering pointless any future aspiration of individual creation someone may have.
The association has been made and it is not going away.
AI in concept is not evil and could be a good thing .
Unfortunately, its implementation has been at the hands of rapacious, avaricious, and narcissistic über-capitalists, which has inextricably linked AI with the evils you enumerated.
In a different timeline, AI was developed slowly, using heavily-vetted and legally obtained data, and rolled out in an intelligent and safe way.
We are better off leaving the appeal to alternate time lines for another conversation, preferably around science fiction or comics.
As it exists, as it was created, "AI" is evil. It consumes resources we can't afford to waste and is currently supercharging our pollution indexes and creating what may be a catastrophic collapse of already very fragile and unbalanced social and economic realities.
And because we are already into the sunken cost falacy fase, it will never be rewritten or rebuilt. Hopefully, it will collapse in such horrifying way it will create a cautionary tale, but we are not so lucky, so what we are left with is picking up the bits after it.
This kind of system had to be developed inside laboratories, colleges, universities, research centers, to aid into very niche and specific fields of research, not made to be a mass consumption comodity as it is. But it was, as you very well put it, not done that way.
AI is not evil. It doesn't have a consciousness. It doesn't make decisions.
What is evil, are billionaire capitalists having full control over the technology.
What is evil, is the concept of closed-source.
What is evil, is stealing all creative works without attribution or compensation.
What is evil, is seizing essentially all the silicon to build these datacenters, then soak up all the electricity out of the grid and all the water out of the ground.
The problem isn't the AI, itself. It's the means that's the problem...not the ends.
load more comments
(2 replies)
load more comments
(55 replies)
If they're just using it to find and patch bugs/exploits? Fine by me.
Vibe coding? Get the fuck outta here.
This is the key point.
From my reading that is not the limit in how they are using AI. It seems like they are accepting LLM generated code as inputs.
This pretty much compromises the whole project as far as I am concerned.
load more comments
(8 replies)
load more comments
(4 replies)
I'd argue that this news is over-blown. The project has more than a solid and honorable track record with insanely talented engineers behind it. AI is a new technology that is not going anywhere. I would put my faith into their decisions to improve this project by whatever means they think are best.
The truth is most commenters are not technically skilled to evaluate or critique their decisions. If GOS team, who again would be at the top % in the field, feel that this can elevate the project, should we not give them the benefit of the doubt?
My thought it was over blown until I saw them claiming that anyone on Mastodon is "not a user" and them saying that any real users are on their Discord and not complaining.
Uh, OK - Discord was semi-excusable up until 2025, but at this point anyone using it to communicate with their users is certainly not considering how bad that channel is for user privacy. Im a Graphene User, I will not use Discord, and I am not going to continue to use an OS thats supporting the rapid expansion of datacenters through the use of AI.
load more comments
(4 replies)
load more comments
(39 replies)
I'm anti-WhateverTheBillonairesArePushing. And by golly are they pushing AI.
GrapheneOS is using AI models to find vulnerabilities before others do. The Bitcoin Red Team did the same and found an absolute ton.
I hate the AI bubble, but they're forced to use AI to defend against AIm
load more comments
(11 replies)
There really is a difference between AI-assisted coding and vibe coding, and I don't know enough about actually coding to look at their repos and tell you what's happening.
load more comments
(2 replies)
A bit unrelated, but I wonder if I'm the only one left that is:
- Using small, open-weight models
- Asking it to only write small snippets that I can easily go through, check and understand.
- Copying pasting from good old web frontends instead of integrating it into my editor or whatever else people do with agents nowadays.
I feel like when we're talking about AI this sort of usage gets lumped into the same pile as agentic vibe coding and it's not helpful for discussion. Surely most people wouldn't find this problematic?
load more comments
(12 replies)
I don't like GOS devs, they are not focused on usablity, but on security (which is completely valid, but it's a shame that GOS is the most usable mobile OS), but holy based.
If you are disputing AI utility in coding: Recent Linux kernel versions fixed up to 3 times more CVEs in comparision to releases before AI. Also, much less of those CVEs are found in the newer versions, which means new kernel releases contain better code.
load more comments
(2 replies)
OSS projects have already started to recognize that LLM is just a tool and how you use that tool matters a lot more than whether you are using said tool at all. Lets bring StackOverflow for analogy: we didn't ban browsers for code development because one can navigate to StackOverflow and copy-paste some really crappy code. LLMs are SO on steroids (actually trained on SO topics). So grabbing LLM to get a sense of direction or shape is an OK use in general, but copy-pasting it's results blindly is silly and dangerous.
There's a second argument that AI is ruining OSS communities which I believe is true, but refusing to accept AI code is a self-defeating action. Why? Because AI training needs unadulterated source of knowledge, one not tainted with AI and OSS communities rejecting AI would be that source. Also: if OSS community did not use AI it would hardly stop it from continuing it's growth in Enterprise. So there's not much of a winning strategy there either.
Which brings us to GrapheneOS decision and given above reasons I think it's a well-balanced decision.
load more comments
(14 replies)
view more: next ›