All About Sun Microsystems Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: QwikSand who wrote (28532)	3/3/2000 8:50:00 PM
From: rudedog	of 64865

QS - I think the problem is in the programming practices out there among the development community, something MSFT has a lot less ability to control. One of the original design goals for Win95 was to develop a common set of APIs and programming practices but as far as I can tell, this got no more than lip service from the development team. Some believe this was the reason that Brad Silverberg, who was responsible for the Win95 effort, left soon after. As a result, instead of promoting the device independent concepts developed originally for NT, the revised Win32 APIs proliferated all of the bad practice from the DOS world. The result was the creation of a huge body of third party code dependent on direct access to the hardware, revising registry entries and DLL components, and all of the other practices which assume the app owns the machine and nothing else is going on... and now that is also the body of code which Win2K will need to support. I don't see any easy way out of that box for MSFT - it's like restoring water flow in the everglades or something... once the base changes are made it still takes years for the problem to get flushed out.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next