There *has* been a lot of talk about the problems with so-called "AI" but one I don't feel gets enough attention is that "AI" products are surveillance products. "AI" is inevitably run in a cloud service, and in order for the AI to know what to generate some amount of the context within your application— usually it's not clear to the user what context, or how much— has to get sent to the cloud. The more of my local app state that gets transmitted over the Internet, the less comfortable I am.
So consider the "Copilot button". I cannot imagine a way this could get implemented that doesn't come down to "there's a trap button on your keyboard that every time you press it, some nonobvious chunk of local/personal information gets sent over the Internet and bounces between multiple corporations". The privacy policy will claim the information is not "retained", but the moment this centralized data pipe exists every intelligence service on earth will have a high incentive to get a tap on it.
@mcc I only just learned a few things the "Windows" button does. I have no idea what the other one does - or what it's even called. It seems to bring up the right-click menu?

@TomF By "the other one" do you mean the rectangle button? I've never understood what that does.

The Windows key serves a very important purpose: Being remapped to WinCompose

@mcc @TomF it's the Context Menu button. it's like a keyboard shortcut for right click, but specific to the behaviour of displaying a context menu. it's used by people who navigate by keyboard alone (e.g. tabbing through controls), often as an accessibility thing.

@gsuberland @mcc @TomF

Well, I navigate Windows by keyboard and mouse and I still use the Context Menu button a lot (I have remapped my capslock button to be the Context Menu), because keyboard shortcuts are fast and efficient if software supports them. :-)