So the issue isn't actually that it's baked into the OS, it's that you should have control over when it's used.
replyI'm not GP, so I can't comment on where their line is, but for me the difference between Copilot and Apple Intelligence is that I can turn off the latter and never see anything about it again. Copilot, on the other hand, is everywhere and it's almost all universally buggy garbage, even when it's disabled.
replyI actually trust the Apple Intelligence, when off, doesn't exfiltrate my data.
Oh yeah and even when you turn off preferences/settings/features in Windows, they mysteriously come back later in one of the unilateral forced updates, against your wishes.
replyYea I respect that.
replyI too would not want any unprompted access to my files.
At the end of the day this issue is that we don't trust the OS and we cannot easily validate how it is designed to behave.
> So the issue isn't actually that it's baked into the OS, it's that you should have control over when it's used.
replyBaked into the OS implies that it's integral to its operation in a way that the two are fundamentally inseparable. Having a global off switch implies that's not true.
There are other irritating baked in aspects of the newest macos and other recent versions that are arguably less avoidable, like Tahoe's entire UI design, or the Settings app.
The real issue is copilot is implemented in their apps inconsistently. Very clear there’s little cross app planning. Apples solution is global and apps and hook into it or not. And if you turn it off apps done break.
replyApple intelligence even when activated is just not as annoying and obtrusive.
reply