> I disagree; the entire point of the Windows key is that it isn't interpreted by applications. It provides instant keyboard-driven access to OS/shell functions (i.e. cross-application functions), and I love it.
I get that, and I understand what Microsoft is doing, but I don't think the two usages are mutually exclusive. So it can be used for all it's current functions, but individual applications could assign shortcuts to Win + [modifier key(s)] + [key] or even Win + [key] (providing warnings if it conflicts with an existing OS/shell shortcut). Users should be able to override existing OS/shell shortcuts for something else if they want. I understand that this means that if Microsoft introduces new Window key shortcuts in future releases, this could potentially conflict with existing application and user assignments, but I think the benefits make this worth it. As it stands, Microsoft is wasting the full potential of the Window key. Maybe there are some guidelines they could establish that would leave things open enough for future releases (e.g. applications shouldn't assign Win + [key] combinations, it must be Win + [modifier(s)] + [key]).
In OS X, you have some cross-application functions using the Command key, but applications can use the key too, and when there is the possibility of shortcut configuration, users can choose whatever [modifier(s)] + [key] combination they want. Granted, many of the usages of the Command key are for in-application shortcuts, but I don't see the huge benefit to isolating a single key for only cross-application functions that is worth giving up a potential modifier key. I'm ok with using multiple modifier keys for new cross-application functions that may come in later OS versions, or sorting out conflicts that may arise. I'm ok with the "cheese" moving a bit, and I think those who aren't wouldn't be heavy keyboard shortcut users anyway.
Maybe there is the possibility for this in Windows already, but I just haven't seen it? Apparently One Note has it's own shortcuts that use the Window key, but that is a Microsoft application, so they may be using private APIs or something.
I haven't been a heavy user of a Linux or X11 GUI in a while, but back when I was, in Gnome/KDE/etc you could assign the Window key to whatever you wanted, and it was mostly unused by applications by default, so I was able to assign it to window manager functions, etc. The defaults of Gnome/KDE seemed to be mimicking Windows. If I went back to Linux, I would try to setup an arrangement more like OS X, or at least come up with something more comfortable for an Emacs user (e.g. Ctrl-V should do page down, not paste; I have setup OS X to act that way through a 3rd party app). The beauty of Linux is that you can configure things how you want it, and you are not stuck with what the OS designer thought was the best idea. I haven't used Ubuntu Unity, but if that happens to be restrictive, there are plenty of other window managers that aren't.
I must admit I feel the same way about Fn keys on laptops: that's another modifier key I could be using that is limited to only a handful of functions.
I get that, and I understand what Microsoft is doing, but I don't think the two usages are mutually exclusive. So it can be used for all it's current functions, but individual applications could assign shortcuts to Win + [modifier key(s)] + [key] or even Win + [key] (providing warnings if it conflicts with an existing OS/shell shortcut). Users should be able to override existing OS/shell shortcuts for something else if they want. I understand that this means that if Microsoft introduces new Window key shortcuts in future releases, this could potentially conflict with existing application and user assignments, but I think the benefits make this worth it. As it stands, Microsoft is wasting the full potential of the Window key. Maybe there are some guidelines they could establish that would leave things open enough for future releases (e.g. applications shouldn't assign Win + [key] combinations, it must be Win + [modifier(s)] + [key]).
In OS X, you have some cross-application functions using the Command key, but applications can use the key too, and when there is the possibility of shortcut configuration, users can choose whatever [modifier(s)] + [key] combination they want. Granted, many of the usages of the Command key are for in-application shortcuts, but I don't see the huge benefit to isolating a single key for only cross-application functions that is worth giving up a potential modifier key. I'm ok with using multiple modifier keys for new cross-application functions that may come in later OS versions, or sorting out conflicts that may arise. I'm ok with the "cheese" moving a bit, and I think those who aren't wouldn't be heavy keyboard shortcut users anyway.
Maybe there is the possibility for this in Windows already, but I just haven't seen it? Apparently One Note has it's own shortcuts that use the Window key, but that is a Microsoft application, so they may be using private APIs or something.
I haven't been a heavy user of a Linux or X11 GUI in a while, but back when I was, in Gnome/KDE/etc you could assign the Window key to whatever you wanted, and it was mostly unused by applications by default, so I was able to assign it to window manager functions, etc. The defaults of Gnome/KDE seemed to be mimicking Windows. If I went back to Linux, I would try to setup an arrangement more like OS X, or at least come up with something more comfortable for an Emacs user (e.g. Ctrl-V should do page down, not paste; I have setup OS X to act that way through a 3rd party app). The beauty of Linux is that you can configure things how you want it, and you are not stuck with what the OS designer thought was the best idea. I haven't used Ubuntu Unity, but if that happens to be restrictive, there are plenty of other window managers that aren't.
I must admit I feel the same way about Fn keys on laptops: that's another modifier key I could be using that is limited to only a handful of functions.