2013-07-17 I've worked with people who develop software systems on Windows. I don't want to talk bad about software that takes different focuses than I do. I don't want to reject Windows just because it ist not Unix. But I do want to judge based on evaluation and ex- perience. You can't verify the correctness of your own point of view, thus my opinion might not be universal. However, I've seen few great sides and effects of Windows and many bad ones. There is this programmer who wanted to performance-test and debug a client-server application. He set up a separate computer for each client. Of course, this approach was limited by design. The de- bugging scripts were actually controlling graphical programs that used a lot of resources. I'm sure this came up from a way of thinking that is motivated by Windows. To me this sounded almost rediculous. Of course, I started multiple instances on one machine -- we have multitasking, you know. Of course I would have created a command line interface to be able to automate every- thing without unnecessary resource-intensive components that you can administer with GUIs only. All this is limiting the testing ability. A Unix guy, someone who thinks in the Unix way (Because Unix is not just a piece of software but a way of thinking!), would automatically used a much more scalable testing approach. In the end, we detected a critical point when having more than 16 clients (run on three machines). With only one client on each machine we would have never come to this point. Still we needed to configure and start each client manually, because it required a GUI. Having a CLI interface and a Unix shell, it would take me less than one hour to automate a testing scenario to run on any single machine to do all this testing automatically and mail the results to the developer. These guys have probably never thought about having such a setup. This is why I am convinced that people need to learn the right, powerful systems. It's not about learning to use these systems but to learn a new way of thinking. To be able to think on the next higher structural level. Altough Windows is not only bad and there's not only (de)light in Unix, it appears to be a good advice to only take developers who use the Unix shell if you want to have good (application) developers. And with ``good'' I mean ``to be able to think in powerful ways''. http://marmaro.de/lue/ markus schnalke