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.

17 of 542 comments (clear)

  1. Can't Resist by Tim+C · · Score: 5, Funny

    What do they mean, Windows would be crippled? ;-)

    Cheers,

    Tim

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

    Here is proof.

  3. Re:What about OS X? by generic-man · · Score: 4, Insightful

    Apple doesn't have a monopoly to leverage, so there is no recourse. For the same reason, Red Hat doesn't get in trouble for bundling various applications with their Linux distribution since they are not a monopoly.

    --
    For more information, click here.
  4. Re:cripple by lysurgon · · Score: 5, Insightful

    The only thing it would cripple is their business model. So in a sense they aren't lying.

    Exactly! But that's an admission of gult there! Check it: the DOJ has found that their business model is monopolistic and anti-competative. Ergo, any solution that would rectify that situation would by necessity cause them to change the way they do business.

    That's why these nine states are holding out, because the current government settlement will not stop microsoft from deploying its monopoly of the desktop in anti-competative ways.

    The problem is that with the influence of Sun and AOL/TW, this case is becoming more about giving up market share to existing competitors (cementing the current plutocratic high-tech oligarchy) and not about opening the field to innovation, entrepeneurialism and true competition.

    Sadly, it's mega-corp vs mega-corp at this point... feels a bit like the last presidential election: you root for the lesser of two evils.

  5. Re:What about OS X? by Dark+Paladin · · Score: 5, Insightful

    Remove iTunes.

    OS X still works.

    Remove iPhoto.

    OS X still works.

    Remove IE.

    OS X still works.

    It doesn't come back and say "No, you can't use Kodak's software - you must use iPhoto!" You don't have to fear something coming back and making iMovie your default application over Adobe Studio (or whatever it is).

    That's the big difference. If you try and remove IE from Windows, Microsoft gets pissed off because that's a big bad no-no, so you have no choice but to have that software whether you want it or not. It was put on to keep their monopoly - not because they thought they had a better browser. (Whether it became a better browser is not for debate here - that happened after Netscape basically was dried up.)

  6. Re:cripple by Brian+Kendig · · Score: 4, Insightful

    That's true, since it's absolutely crucial to Microsoft's business model to avoid giving any ground to any of Microsoft's competitors.

    Microsoft will *not* release a version of Windows that's stripped-down with the browser removed. Period.

    They will assert to the end that it's simply not possible for them to do. Eventually the government will require them to, but then they'll do like they did during the court case in 1999 and make a version of Windows which simply doesn't work, and they'll point to this as proof that they were right all along.

    When the government continues to require Microsoft to release a version of Windows that doesn't have IE bundled in, Microsoft will continue to not offer such a product. The court case will drag on for another seven years. If eventually Microsoft is backed into a corner and somehow *forced* to offer a stripped-down version of Windows, then it'll be more expensive than the standard version, have more bugs, and PC makers will face stiff penalties from Microsoft if they use it. And then *that* court case will drag on for seven more years.

    Meanwhile, Microsoft will misrepresent this to the public as 'the government is trying to get us to remove useful software from Windows and not let you have it for free!'

    The real problem is that Joe Sixpack doesn't understand the big deal. He gets Windows with his PC, and it comes with a web browser and an instant messager built in, and any great new killer apps to appear in the future will have a workalike clone also built into Windows so that he doesn't have to go figure out how to download and install it. He doesn't understand that he's paying for these 'freebies' in the cost of Windows, which is part of the cost of his PC. He doesn't understand that without competition these handy utilities won't be any better than they need to be, as long as they're not so bad that he is driven to figure out how to download/install other companies' software.

  7. Re:Thats funny by Edgewize · · Score: 5, Insightful

    I don't know what kind of world you program in, but where I code, componentisation and coupling are not even close to the same thing. For example:

    Mozilla encourages use of its components. Anyone can use the rendering engine and distribute it with his own product, saving on development time while still providing a product to the widest possible market.

    Internet Explorer promotes coupling. Anyone can use its rendering engine, except that nobody is allowed to distribute its rendering engine except as part of the full Internet Explorer package. This cuts down on development time at the cost of forcing all your users to run Internet Explorer.

    See the difference?

  8. How does this compair to linux? by FortKnox · · Score: 4, Interesting

    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).

    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.

    So, the professor is correct that THEORETICALLY there is modularity that's simple to seperate.

    It always gets me when people ask professors about stuff that a business does. Like this. Most professors (note: I said "most", not "all") go to school and get their bachelors, then grad school for masters and PhD, then off to teaching. Most haven't had much of a job outside the schooling system. Sure they know the theory expertly, but theory and practice, as always, are different.

    --
    Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    1. 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
  9. Easily defended by mjh · · Score: 5, Insightful

    Unfortunately (or fortunately, I guess depending on your perspective) this is probably pretty easily defended. The difference between an embeded OS and a consumer computer OS is pretty significant. In the embedded OS, you can take out a bunch of features and not consider the OS to be crippled. Whereas the lack of those features in a general purpose consumer computer would make that OS crippled.

    The reason is that in the embedded space, the OS tends to be used for very specific services. Thus removing any services not related to the one being provided does not cripple the OS. But in a general purpose computer, as the name implies, the OS is expected to do a huge variety of things. Hence losing some of those features would cripple a general purpose OS, but not cripple an embedded OS.

    An analogy: an automobile that came with no radio, no cup holders, no airconditioning, a net instead of a drivers window, and no doors, would by consumer standards be crippled. However those same things that cripple a consumer car are requirements on a car that's going to race for NASCAR.

    So while it's interesting to see that MS *can* modularize their system. It's not a very compelling argument.

    (Just a minute, I gotta get on the asbestos suit on... ok flame away.)

    --
    Key to financial independence: Spend less than you earn. Save and invest the difference. Do it for a long time.
    1. Re:Easily defended by rhizome · · Score: 4, Insightful

      You're playing right into Microsoft's game: it's not the OS that would be crippled, but the *product*. Microsoft markets Windows almost as a suite of functions, and to take any of those away would necessitate their changing their marketing stragegy that has evolved over years and years. I'll repeat: Embedded Windows seems to use a modular structure much like UNIX, while consumer Windows is a branded, packaged set of functions. It would not "cripple" Windows if Media Player was de-integrated. It would not cripple Windows if Notepad was left out (edit.com is just as good ;). It *would* cripple their product vision, however, because consumers would become aware of the changes and have cause to reflect upon the usefulness of Windows as a whole. Many many people see Windows as a single entity, if they recognized that any OS is basically a hardware handler with whatever frills happen to be included (or available), then they could become smart enough to choose something else. It runs counter to an entrenched market leader's interests for people to have a benchmark to compare OSes where before there was only one OS. Users who are able to ask themselves or their friends if they really need some particular feature of what they're buying are Microsoft's nightmare.

      --
      When I was a kid, we only had one Darth.
  10. 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.
    1. Re:The technical issue is NOT about modular design by killthiskid · · Score: 5, Insightful

      However, as such programs as 98Lite show, you take the IE out of windows and still leave the ability to render html, by leaving the html rendering dlls registered and on the machine.


      So, not IE, no active desktop, and the ability for apps to still use built in html rendering. Isn't this what we are looking for? Then any program could be the browser, MS would just be providing the guts.


      I think that this is what MS is afraid of. They want control of the browser becuase it roughly equels control of the internet (for the average person).


      Ever notice what happens when you upgrade IE? The first screen you get when IE is fired back up is a request for the user to change the home page to MSN. This is a big deal in terms of driving traffic to MSN.


      This grip on the internet via IE also allows MS to embrace-and-extend... which they could still by controlling the abilities of the html rendering dlls...


      You're right about one thing: it is not a technical issue. It's about control.


  11. Re:Prof. Appel's contradictions by Fiver-rah · · Score: 4, Interesting
    I'm not sure I buy this. Appel says:

    Because computer source code is an expressive means for the exchange of information and ideas about computer programming, we hold that it is protected by the First Amendment.

    Now if Microsoft wanted to release the source code to their IE/Windows, I don't think Appel (or anyone here) would argue with their right to do so, even if IE and Windows were inextricably tangled. Clearly, that isn't going to happen. The issue is over the executables they release. Which are not protected. The Windows CDs which MS provides do not provide for the exhange of information and ideas about programming. As a matter of fact, the EULA you have to accept to run this software specifically binds you not to try to figure out how it works. No sane person would consider a non-human-readable executable to be protected free speech. Come on.

    --
    Read Bujold. Free (as in
  12. Re:cripple by unformed · · Score: 4, Funny

    but then they'll do like they did during the court case in 1999 and make a version of Windows which simply doesn't work.

    As opposed to all the other times when it did work.

  13. Like gasoline tax stickers... by Marx_Mrvelous · · Score: 4, Insightful

    Each PC needs to have a sticker on it that says "$120 of the price of this PC goes to Microsoft for its products" like they have for the $.33 gasoline tax here in Indiana.

    --

    Moderation: Put your hand inside the puppet head!
  14. 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.