Commentary

Serdar Yegulalp
 

Criticizing The OLPC (And Its Critics)

Jon Evans of The Walrus didn't like the OLPC. He thought it was the wrong tool for the job -- badly engineered, improperly envisioned, and more hype than substance. The OLPC folks didn't take that criticism lying down, but their response is in many ways just as narrow-minded as some of Jon's criticisms.

Jon Evans of The Walrus didn't like the OLPC. He thought it was the wrong tool for the job -- badly engineered, improperly envisioned, and more hype than substance. The OLPC folks didn't take that criticism lying down, but their response is in many ways just as narrow-minded as some of Jon's criticisms.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Jon was disturbed at how the XO was so unlike his Acer Aspire One, or any number of other commodity-computing netbooks (many of which, it has to be said, were inspired by the XO's original premise). He hated the Sugar platform; hated the keyboard; hated how Web pages didn't seem to render correctly in the XO's browser. "A collection of badly executed good ideas," was how he put it, in sum, and he's not the only one who thinks the OLPC Project has missed it mark.

Whatever you might think about Jon's criticisms -- good, bad, misinformed -- I don't believe for a second they deserved the kind of response that appeared on the OLPC News blog (which is, as I've since learned, not affiliated with the OLPC project). When he groused about the Wikipedia issue and the fact that encrypted Wi-Fi connections didn't work right, they wrote: "Apparently for Jon, the computing key to revolutionize education is to connect to encrypted Wi-Fi networks so children can read properly formatted Wikipedia entries."

The rest of the article's tone is only marginally better, and while there are some legitimate points -- e.g., cell phones are not a substitute for notebook computers -- the tone is a massive turnoff. Instead of listening to someone who might have had something to tell them, however bitter a pill it might have been to swallow, they snarked right back and called him "unqualified" to comment on how to deliver educational technology to children in developing nations.

It's an echo of the same kinds of defensive guff I hear fired off in other corners of the open source world: "Obviously, the problem is you." No, the problem is that even badly worded criticism can be useful, and you need to not be so thin-skinned as to not hear any of it when it comes your way.

If, for instance, the Mozilla team was in the middle of prepping Firefox 4, and someone wrote a scathing review of the beta -- do you think the Moz people would respond by merely being snotty and dismissive? I'd like to think not; they have a better sense of how to engage their audience and critics than that. It's a skill worth learning no matter what your business.

(And if they have ever been like that, I'd love to know. It would make a great addendum.)

[Addendum: The other blog in question is in fact not affiliated with the OLPC project, and I've amended this post to reflect that. I still think my notes about the tone of both the original criticism and the countercharge apply, however.]


Follow me and the rest of InformationWeek on Twitter.


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