>From what I can recall while working at SolidWorks (still called Winchester Design at the time), they had an extremely hard time getting developers to adopt to NT, and the initial hardware platform it should be run on was in question too.
The concepts were so new to the Windows-world that it would have stymied growth or killed the business completely. Microsoft's goal was to make/sell a networkable OS to compete with *NIX, and be as easy to use as Windows. They accomplished this goal, but as the *NIX world has always been quick to point out, they F'd us at the same time in terms of security and non-GUI administration. This is all to the best of my recollection from my NT 3 beta testing/development days. YMMV. -- ME2 On Fri, Jun 5, 2009 at 10:46 AM, Ben Scott <[email protected]> wrote: > NT could run Win16 code. It just didn't allow system operations > without admin privileges. Exactly how much of a problem that would > have been, I can't say. It's certainly still a source of trouble > today, so that doesn't bode well. But think of how much further along > we would be *today* if Microsoft as a whole had started to consider > security important back then, rather than starting in 2001. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
