Slashdot Mirror


Professor Testifies Windows Is Modular, Separable

circlejtp writes: "Princeton University professor Andrew Appel said in written testimony that modular design is an accepted standard in the industry, and Microsoft has already created a version of Windows for interactive television boxes that has removable functions. The full story can be found on the Tacoma Tribune website." At issue is Microsoft's claim that separating Windows' components would cripple the OS.

9 of 542 comments (clear)

  1. Sure it's modular... by Skweetis · · Score: 5, Informative

    Here is proof.

    1. Re:Sure it's modular... by Reziac · · Score: 3, Informative

      Um.. you DID notice that 98lite and IEradicator are for Win95/98/ME, and have not yet been released for Win2K, right?? And you DO know that Win9*/ME and WinNT/2K are very different animals, right?

      Just went to 98lite.net and checked -- nope, not available for Win2K yet. Tho I've heard it's in the works, and an XPLite version is expected to follow.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  2. Re:What about OS X? by Gehenna_Gehenna · · Score: 3, Informative
    Maybe because you can remove/uninstall iPHOTO/iMOVIE/iTUNES and still have a fully functional OS. Not so w- IE, which is intigrated as Windiws file browser AS WELL AS an internet browser.

    I could be incorect though.. this is just speculation on my part.

    --

  3. Re:What About KDE? by evilpenguin · · Score: 3, Informative

    The fact that konqueror is not integrated. You don't have to have konqueror to use KDE. Also you don't have to have KDE to run Linux. You don't pay anything for either of them, and finally, KDE is not a monopoly.

    The whole issue is the "tying" of IE (at the time not a monopoly product) to Windows (a monopoloy) for the sole purpose of harming a competitot (Netscape). If this isn't clear to you, then I suggest you are not up on the issues.

    Read the Findings of Fact in the case. The present debate is only over the remedy. No one has successfully challenged the findings of fact. Read. Learn. Enjoy. Then come back and tell me there is no difference between the two.

    Ignorance is bliss and we are a happy country.

  4. Re:What about OS X? by david+duncan+scott · · Score: 3, Informative
    No, they're applications.

    Bit of history, because we're all forgetting this stuff: Back in the day, Netscape's claim was that Navigator was more than a browser, that because of its plug-in architecture people would write applications that would run under Netscape. Since Netscape ran on multiple OS'es, applications written to Netscape API's, rather than OS API's, would be portable, rendering the underlying OS irrelevant, or at least much less significant. This "middleware" aspect to Netscape -- a platform on the platform -- was what frightened Microsoft (according to Netscape, mind you), causing Bill and company to come after Netscape with chains and knives.

    iWhatever, AFAIK, are simply programs that do stuff themselves, not platforms upon which other programs are to be built.

    Ah, but you say that you've never seen a database or word-processor written as a Netscape plugin? Me neither, nor did Netscape ever bring one out and show it to people as a proof-of-concept. Still, they convinced the court.

    --

    This next song is very sad. Please clap along. -- Robin Zander

  5. The technical issue is NOT about modular design by Ryu2 · · Score: 5, Informative

    When will you guys understand? Windows has always been modular, in that it separates functions nicely into DLLs which export APIs and can be replaced or removed as needed. It's rather that as a standard part of Windows, many MS and non-MS apps use components from IE to do various things, like render HTML (including many non-"web" apps that use the HTML renderer as a quick way to have a nice UI), or do network stuff like HTTP queries without having to "reinvent the wheel" with each app.

    If you remove IE (meaning all the dlls that form it, not just the stub executable which is little more than a front-end to the underlying HTML rendering and networking DLLs), sure the OS will still run and you could definitely still use it as a server, BUT a lot of user-level stuff like the shell and applications, not just IE, would suddenly break. So even if it were removed, you would need to have some sort of other implementation of the functionality that IE provides to other apps via COM.

    --
    There's 10 types of people in this world, those who understand binary and those who don't.
  6. Re:What about OS X? by Aexia · · Score: 3, Informative

    My problem wasn't that MS was bundling IE with Windows. That's the media's gross oversimplification of the problem.

    The problem was Microsoft leveraging their near-OS monopoly to bully OEMs and competitors. The bundling of IE was just part of that attack strategy.

    Apple, of course, doesn't have any OEMs to bully nor a desktop monopoly to leverage. That's the difference.

  7. Re:How does this compair to linux? by Boulder+Geek · · Score: 5, Informative
    How modular is Linux? How easy is it to pull apart the pieces? (I honestly don't know the answers, so input would be great).

    Pretty easy, depending on how you define Linux. The kernel is a monolithic kernel made from many modules. The rest of the system is just a bunch of programs that depend on various shared libraries. In this regard Windows is essentially identical, other than the fact that MSFT refuses to distribute various key components independant of particular applications, even though other applications use those components. This is why MSFT continues to maintain that Windows would be crippled if IE were removed. They are claiming that components such as the html renderer cannot be distributed without IE. This is contradicted by the fact that many applications use that component and no other part of IE.

    Honestly, coders strive for modularity on almost every project. Theory says its possible, but anyone that's worked on a large OO project knows that there is always an exception (usually a dozen) to the rule, and "seperating" the modules is a lot more work than you'd think.

    MSFT uses COM to export various modules from programs like IE. All of these modules have well-defined interfaces that can be used by other programs. By definition these parts are modular, and have no dependenciels other than (perhaps) on other COM modules. Any spaghetti is hidden behind the COM interface. In the UNIX world we sort of do the same thing, in that code that is meant to be shared is put into shared libraries and usually packaged separately from the main application.

    --
    A well-crafted lie appears unquestionable - Dama Mahaleo
  8. Re:cripple by blibbleblobble · · Score: 4, Informative

    Who cares about a Windows without IE6? Let's start with a Windows that it's not illegal to sell as dual-boot Windows/Linux from computer shops.