Commentary

Paul McDougall
Editor At Large, InformationWeek  

Should One Laptop Per Child System Run Linux Or Windows?

Microsoft stirred up controversy last week when it suggested a Linux-based laptop for children in developing nations be redesigned to accommodate Windows. Would that be a good move?

Microsoft stirred up controversy last week when it suggested a Linux-based laptop for children in developing nations be redesigned to accommodate Windows. Would that be a good move?One Laptop Per Child's XO system currently runs on a Red Hat Linux OS. The thinking is that open source software allows OLPC to offer a system for the lowest cost possible. It also prevents 'lock in' to any one commercial vendor's technology.

But Microsoft general manager James Utzschneider argues that making the XO laptop compatible with Windows XP would give students in poor countries access to "tens of thousands of existing educational applications written for Windows."


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

That sounds like a reasonable point -- after all, there's not many Linux apps out there aimed at the K-12 market, in any language.

Utzschneider says a shrunken version of Windows XP could potentially run on 2 Gbytes of flash memory. The XO, however, can only hold 1 Gbyte. As a result, Microsoft wants the XO's designers to add a slot through which more memory can be added via a Secure Digital (SD) card.

So, what do you think? Would kids in the developing world be better off with a Linux-based system that goes for under $200?

Or, is it better to equip them with technology from a major vendor that's supported by an ecosystem of thousands of application developers -- even if that means the system might cost a bit more?

You can weigh in below with your thoughts.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links