You can also enter Expose, the CMD-Tab or use the dock and without leaving Expose, it will switch the windows being shown from App to App.
----------
An often misused word. Workflow is about daisy chaining tasks together, not about the keyboard/mouse/trackpad short cuts to do so.
In programming, a typical workflow would be :
- checkout source from the repository
- open a file in an editor and add/modify code to it.
- run it through its build environnement to rebuild a binary for debugging
- run it through the debugger to make sure it's behaving as it should
- repeat 1 to 3 as many times as it takes to solve Bug Report or Change Request
- commit source modifications back to the repository, tagging the new release along the way
- run it through its build environnement to produce a release build
- distribute the build to Q&A
That's a workflow. That workflow can be accomplished on any number of platforms, for any number of applications for any projects. Listening to some people here, a workflow sounds like it's :
- cmd-tab to application
- open file
- All Windows Expose to find the duck picture
- All Windows Expose to find the flower picture
- Hit spaces to move some windows around your desktops
Where do you guys actually get any Work done in these Workflows ?
I can get my work done on OS X, Windows, Linux, no matter what GUI/Editor/shortcuts/input devices I have. That's because my workflow is not something that is tied to UI candy for switching applications and moving windows around. My workflow is a flow of tasks. These tasks might differ in how they are accomplished, but the tasks themselves remain the same. I just adjust to the platform instead of trying to adjust the platform to myself.
Workflow includes how the work gets done. If you had to go into Terminal and type in a 15 pin identifier that was randomized and unique every time you wanted to send an e-mail it would interrupt the flow of you work whenever you had to send an e-mail. Would e-mails get sent? Sure, but it would be a poor design and worthy of criticism.
Mission Control adds additional steps and complexity to what was a seamless experience. Mission Control has severe deficiencies but you never address those deficiencies in your defense of Mission Control, you just say that it doesn't matter because the end result is the same. That is like saying eating at McDonalds is the same as eating at Farm Burger because you aren't hungry after you've eaten.
Process Matters, Quality Matters, Experience Matters, Details Matter. Read the Steve Jobs book, you will see a person whose entire existence was consumed by those principles.
Windows != OSX != Linux != MS-DOS just because you managed to get your work done.
----------
Heck, most of MacRumors user base isn't tech savvy. Most of them are Image editors/Video editors/Photographers who have no clue how a computer actually works, what a OS actually is (they think the GUI layer is the OS, they have no idea of everything else that sits between those pixels and the underlying hardware) or even what a Profession is (thinking Image editors/Video editors/Photographers are the only professionals out there).
The purpose of a personal computer is to react to the user. Apple's Developer Documentation clearly shows that the main focus of OSX is to respond to user events. While there is a butt-load of amazing programs running behind the scenes, the ultimate purpose of a personal computer is to give the user the experience the user needs. Whether that is making an spreadsheet, running a server, protecting the file system, etc., the ultimate requirement is that the User's needs are fulfilled. One of those needs to have the experience of using the computer be seamless and without needless hassles.
Another need is that the sophisticated workflows of Image Editors, Photographers, etc. be enabled without knowing the details of the underlying OS. It should "just work"