Partially because Defender does a lot of unnecessary work. Partially because Explorer now has Chromium under the hood of many elements.
Also Copilot. Not even joking. Having so many copilot buttons in apps is not an issue. The issue is to actually try using it. Even a light conversion crashes both the desktop an Android clients too often. At this point I would rather have those resources consumed by actual AI running locally than on a crappy frontend. Pathetic.
These are just NPUs. They can run AI models, but you are not allowed to run actual Copilot as it is a cloud-based product. You need to research and set up AI models yourself if you want to put that to use.
I also don’t expect that [Chromium + idiotic webdevs] formula will not work on those PCs, so Copilot+ PCs will not save you from Copilot crashes.
Partially because Defender does a lot of unnecessary work. Partially because Explorer now has Chromium under the hood of many elements.
Also Copilot. Not even joking. Having so many copilot buttons in apps is not an issue. The issue is to actually try using it. Even a light conversion crashes both the desktop an Android clients too often. At this point I would rather have those resources consumed by actual AI running locally than on a crappy frontend. Pathetic.
Don’t they have the whole “copilot+ ready pc” branding thing now for computers with npus? is none of it actually local yet?
These are just NPUs. They can run AI models, but you are not allowed to run actual Copilot as it is a cloud-based product. You need to research and set up AI models yourself if you want to put that to use.
I also don’t expect that [Chromium + idiotic webdevs] formula will not work on those PCs, so Copilot+ PCs will not save you from Copilot crashes.