[mdlug] Is Vista going to be the new Windows ME?

Ingles, Raymond Raymond.Ingles at compuware.com
Wed Jan 31 14:52:27 EST 2007


> From: Jeff Hanson

> I think the problem is the legacy code base.  Gates has always
> believed that backwards compatibility is an asset.  But it is also a
> liability.  It prevents them from making radical changes to the file
> and security structure.

 To be precise, it's not the legacy codebase of the operating system itself
that's the problem. From the beginning, the NT kernel has been *capable* of
supporting security as well as any Unix kernel.

 But MS has never, at any point, really exercised that capability. They've
grown from a single-tasking, single-user OS with no security whatsoever,
and they've prized backward compatibility that whole time. What security
they've managed to impose is nearly accidental. It's certainly never been
a priority - backward compatibility has been a priority.

 And they've done *horrible* things in the name of backward compatibility.
Part of this article covers some of the truly frightening lengths they've
gone to:

 http://www.joelonsoftware.com/articles/APIWar.html

> I think the best they can do is start over and use virtualization for
> legacy apps.

 They might do that with their 64-bit system eventually. There's some
indication that they are willing to break or impact backward compatibility
there.

 Sincerely,

 Ray Ingles                                           (313) 227-2317

 "The computing industry is given 12 months to deploy a technology
 that does not exist and whose sole purpose is to protect profits.
 The car industry was allowed decades to deploy safety features such
    as seat belts and air bags that were designed to save lives."
   - Zeinfeld, on the SSSCA, a proposed law that would mandate all
 computers to prevent any file copying whatsoever unless explicitly
          approved by the entertainment conglomerates
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 



More information about the mdlug mailing list