zlacker

>>beezle+(OP)
So far in the last year or so, I've heard 0 reasons why I'd even need, want or benefit from Win11 over Win10. Tons of reasons in the negative column though. There isn't even anything to salivate over that might make you think it might be worth it to deal with the other tradeoffs. Hard pass.

>>cronix+Te
I updated to 11 on my laptop but kept 10 on my main machine. I see zero reason to update my main computer to 11. I was willing to give centered start button a try but the fact that you can't turn off grouping of applications in the taskbar is a deal breaker. If I have two firefox windows open I want to know it and to be able to pick which one I want without having to hover my mouse over the icon for a second while the picture of the windows pops up.

So I installed Explorer patcher to get the old taskbar back https://github.com/valinet/ExplorerPatcher

Other than that the only feature of 11 that I have used is the snap zones. And I guess if I want that I can install the power toy it is based on.

>>jccalh+Ys
It could be worse. You could be on MacOS where Cmd-Tab switches between apps not windows. I currently have 13 browser windows open (each with 3 to 15 tabs) and another 9 windows of other things (terminal, vscode, etc....) and IMO The Cmd-Tab vs Ctrl-Tab vs Ctrl-Up vs Ctrl-Down suck compared to Windows. I really want to easily switch to the previous window, not the previous app. Command + backtick doesn't work either. It doesn't switch to the previous window. It switches to the previous window "in the same app" which is not actually the previous window as that could be from another app.

>>greggm+If1
Hmm, I find it pretty practical, cmd-tab from one app to another, cmd-backtick to toggle between windows, I mean, it's a different paradigm, sure, but you can still move around from the keyboard? I do find it a little annoying that there aren't consistent shortcuts for moving between tabs in everything that uses them, could be cntrl-tab, could be alt-arrows...

>>blacks+gk1
I don't love it (yet). It's probably a combo of my Windows background, my ignorance of MacOS tricks, and actual limitations/flaws.

* Cmd+~ from a fullscreen window does nothing, and non-full windows of the app cycle only among each other. If I have fullscreen windows anywhere in my setup, it breaks my flow and (afaik) makes me mouse to the Window menu. I feel like MacOS's fullscreen paradigm is more to blame here, because it violates a range of other behaviors I'd expect.

* Unlike cmd+tab, cmd+~ doesn't give me a visual overview of my windows (how many? what order?). I can see why, since cmd+tab shows only icons and app names, which isn't enough to differentiate between windows of the same app (unlike alt+tab on Windows, which shows thumbnails, paths, page titles, etc.

* Cmd+~ also cycles in a static order, not most recently used. This feels like fallout from the second point, in that if you're not showing thumbnails it could get confusing.

The first one in particular took me a bit of time to realize; before I did, it just felt broken and made me not rely on cmd+~ at all.

>>Propha+KP1
You’re totally right that fullscreen breaks cmd ~. It also breaks cmd tab in unexpected ways.

You’re also right about lack of visual feedback, which is disappointing given the various stuff that I think is still currently branded Mission Control, where obviously the fundamentals are already there.

Cmd ~ isn’t statically ordered though, it’s either application specific or based on recent use in a weird (easy to confuse) heuristic. It follows a similar (maybe identical?) pattern to recent use for cmd tab, and even app switching on iOS.

>>eyelid+Wk2
To your third point, is this a setting somewhere? I tested before I posted w/ 4 Brave windows, but they stay in the same order.

Makes sense, since cmd+~ immediately switches on key down to the next window; cmd+tab (like alt+tab in Win) lets you keep the selection open and choose an out-of-order app, which alters the MRU. How would you do that here? The only way I've affected it is creating/killing windows at points in the cycle. Using cmd+shift+~ for me just goes backward in the same static order.

>>Propha+r33
Some kind of interaction with the window usually (again can be app specific) … reverses the order to the window where this sequence started, then may or may not continue the original order.

I’ve seen this most consistently in apps where I commonly have too many windows open, VSCode iTerm and Chrome being the worst offenders. Edit: my worst offenders, the apps don’t do anything unusual here.