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?
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.
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 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.
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 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.