"I'm talking about people who historically work with Big Iron, or smaller Sun or SGI systems -- in UNIX. To send an engineer into the wild with no UNIX training is not a good idea."
Thats what I figured - What percentage of college graduates do you figure are "people who historically work with Big Iron, or smaller Sun or SGI systems " ?
How many engineers does, oh, say General Moters employ ?
How many would be fired immediately if they started monkying around with the inner workings of their networked CAD design programs ?
You're being obtuse. These are fields that use UNIX, and an engineering grad with no UNIX experience might have a hard time. Someone educated solely on Windows might have a problem being dumped in front of a mainframe.
How many would be fired immediately if they started monkying around with the inner workings of their networked CAD design programs ?
Or how about just maintaining those systems? I also know a nuclear engineer who had to do a lot of UNIX programming as part of his engineering job.
Microsoft might be good for the general purpose computing world, but you need to know UNIX if you're going to work with mainframes, supercomputers or high-end workstations.
Sorry, there are a couple of Windows supercomputers, very expensive, and very low on the list.