|
>There was no concept of "well behaved" Windows code >until the whole .NET thing; There was absolutely dos and don'ts. Do use documented APIs, Don't access internal structures or hardware. That's not to say you couldn't do it, there was no OS or hardware-level prevention of the "don'ts", but MS has always been good at moving APIs forward. Undocumented things are, well, um, undocumented. Now I grant that it was quite often necessary to do things that were undocumetned to do "cool" things, but not to do the things Windows was designed for at the time. >Don't lay this crap on the programmer; it's the fact >that the OS was never really a business OS. Sure, I'll admit Windows 3.1 wasn't ready for business, heck the entire 95/98/ME line was a joke. But the NT/XP line, and 2003 Server is a wholely different beast. You're complaining that a Ford Model T was a pleasant toy, so a Mac truck isn't a good business machine. -Walden ------------ Walden H Leverich III Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.