just get rid of windows 8. as troll as this comment may sound...
I'm not aware of the grouping functionality changing between 7 to 8, at least to the extent that 8 doesn't group more aggressively than 7.
In both operating systems you can customise whether applications are grouped or not.
And although it's not necessarily PuTTY's job to change because of a new feature in the OS (taskbar grouping), I'd note that there is an API for controlling it [1].
[1] http://blogs.msdn.com/b/oldnewthing/archive/2012/08/20/10341...
Note: I'm well aware of workspaces, but that can't be what you're referring to, as they are available to Win users, and it's not clear the OP is looking for anything more than tabs, which a WM isn't generally providing.
[0] http://en.wikipedia.org/wiki/Tiling_window_manager#Microsoft...
Try XMonad on Linux. It does allow me to manage my windows better.
Not that a tiling manager is going to be of ANY help in OP's case; I really doubt the auto-scaling and tiling of his windows is what is making him struggle with dozens of PuTTY instances.
No. It doesn't. Windows has one GUI and various themes for it; Ubuntu has multiple GUIs. That's what a WM is in Linux terms: A whole new GUI that sits on top of very basic graphical primitives which don't determine anything about how a GUI looks or works.
That's like saying tabs should not be in Chrome/FF and Windows/OSX/Linux flavor should handle all of your browsing windows just fine.
Things like tmux would also be a bad thing in your world, the window manger should handle this!
GP needs a putty manager (many exist) and will solve his needs. Much like other programs across multiple OS's solve the same need
It's $99, but I've easily saved 1000x that amount by being able to quickly script shell interactions that don't easily lend themselves to the regular scripting tools like 'expect'.
I think the best example was where a distributed cache cluster was dirtied during a deployment. Dumping the entire 100TB+ of good data was not an option, it would have taken days to warm back up. The cache admin tool had a menu system and wouldn't buffer input, so I couldn't just dump a buffer of commands into it and wait for it to finish.
I was able to lookup recently accessed DB rows in SSH tab #1, compare them to the cache in tab #2, and invalidate in another in tab #3. Problem solved in <20 minutes. We eventually built an app to invalidate dirty cached results, but that took about a week to do it the right way.