this post was submitted on 28 Apr 2026
126 points (96.3% liked)
Technology
84222 readers
3572 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I see people commenting like it's always a bad idea to implement AI. I think it can be a very useful tool and running locally seems beneficial. Is there no right way to do this?
What's wrong with providing it as a package? Why does it have to be part of the OS?
I don't know enough to know the benefit of doing it within the OS vs just a package.
Imagine that OS is your apartment that you rent in an apt building. Your landlord/super announces he's going to install a home robot in every apt.
The difference is whether someone else should put something like that in your apartment, or whether you should get something like that if and when you want it. It's not a toaster, it may have the ability to throw your cat into the trash chute.
A package is simple enough to remove. But almost everything that shoves AI down your throat makes it every difficult to remove it. Certain rollouts have been heavy handed and people kinda just want choice not force.
Know that scene from Finding Nemo with the seagulls? AI. AI AI AI AI. Every app, every device, every site and service. Then your OS (the last and possibly dying vestige of "I control this, this is mine"), esp one built on ejatbised to be touted as Choice.
Anyway, all depends on how it's implemented.
Ok that makes sense - thanks for the example. If done with a package could it function the same way (do everything) as if it were part of the OS? Are there any efficiency gains if AI is part of the OS? If not, it sounds like I'd always just want a package and never any AI built into the OS.
I don't think efficiency would be the thing, but I suspect that a generalized package could have trouble accessing certain distro specific/unique things. Some packages don't have 100℅ compatibility with every distro.
That said Ubuntu's very ubiquitous/popular and tends to be top of the list when you're looking at the compatibility list of an application, so I think it's the least likely to have trouble.
But... I'm answering generally here from a systems perspective, not a developer's. There might be quirks about how a native vs added package can/does interact with an OS... And I'm joking someone else can chime in
I view it a bit like going from command line to graphical. Technically the graphics is all seperate but the experience has been brought in to installation of the os and most function. I think ai will be like this but it will only be something I would want to try with a high trust provider. Not sure canonical is that for me.
If it's local, unobtrusive, and optional, I don't see the issue. I'm thinking like the full line code completion in intellij, that's actually useful.