Silicon Investor (SI) -- The First Internet Community

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 : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?

To: dybdahl who wrote (64318)	1/21/2002 6:04:48 AM
From: Bill Fischofer	Read Replies (4) \| Respond to of 74651

It's a question of differing design models. Unix has its roots in the world of timesharing in which hardware was expensive and "users per processor" was the key design metric. Windows has its roots in the networked PC world in which hardware is cheap and "processors per user" is a more apt design assumption. To use a telecom analogy, Unix was designed for a world in which each household shared a single telephone while Windows assumes each family member has their own cellphone. Which model better matches the realities of the 21st century? Windows will never be as good a timesharing system as Unix because there is no reason for it to develop such capabilities. Hardware is still riding Moore's law and processors continue to get ever cheaper and more plentiful. In such an environment to focus on a timesharing model would be a poor business decision on MSFT's part. Windows easily handles the nondisruptive deployment of new versions of programs in a network model. This is done through group policy which allows administrators great flexibility in controlling which users migrate and on what schedule. So the function is there, just implemented under different design assumptions.

To: dybdahl who wrote (64318)	1/21/2002 10:13:44 AM
From: Jordan A. Sheridan	Read Replies (1) \| Respond to of 74651

Dybdahl; Actaully, Microsoft is well on the way to offering this functionality via the Active Directory and group policies ...I know this is not the exact same behaviour that you have described, but with AD and group policies, the administrator simply publishes the application package to a target group, and each user logs in, the new application is automatically installed...As far as the user is concerned, they see nothing happening except that they log off after using the old version and the next time they log in, the new version has been installed... Regards; Jordan