Post a Comment
So why they make interface for stupid then??? I mean OLPC looks in pictures as horrible as BoB(Microsofts kids UI). Kids dont want have kids stuff, they want same stuff and adults. Underestimating kids learning skill by making interface like OLPC is just gonna keep them away from it. Let them have Windows-type system not some dump kids only UI.
We shouldn't assume these kids are incapable of using a standard interface. I'd argue that they are just as capable of learning how to use a functional computer as kids in developing countries. The proposed "Sugar" interface is both aesthetically and functionally displeasing.
The $100 laptops have demonstrated they can handle the full-featured Fedora Core operating system. So why not give them the real deal?
That's a silly position to take, as the children who end up using these laptops will be trained in an entirely different UI then the reast of the world, and then when they get older, and less flexible, they may have problems adadpting to the way everybody else does things
Yea, it's totally stupid. Just cause these kids are poor doesn't make them stupid.
This is exactly what I was afraid OLPC would have been if it'd run on Windows: A crippled platform that only allows people to learn its own paradigms and not useful things in using other software (the software of the future).
If you give the kids a box, some cds, and reading material in their language they'll figure it out. They're not stupid. Heck, they might even do it without the reading materials if you explain typing and that the cd contains information for the computer to use.
That's a silly position to take, as the children who end up using these laptops will be trained in an entirely different UI then the reast of the world, and then when they get older, and less flexible, they may have problems adadpting to the way everybody else does things
If the point of these units was to teach kids to use Windows, I would agree with you. In fact, the purpose of computers in schools (my kids vary in age from preschool to middle school) is not to teach them to use "computers", but to teach them. Period.
Computers are a tool to learn other concepts. These should be easy for the kids to use in the environment they will be using. And it looks like they are relying on the peer-to-peer "mesh" network to collaborate and share learning experience in the classroom. A traditional "desktop" metaphor is clumsy at that. Well, certainly more clumsy than this UI seems to be. Sugar seems to be (besides very different for our older [fossilized?] brains) well-suited for a collaborative learning experience of the mesh network. Kids are grouped by friends (learning partners) and by task (assignment).
Just because it is very different, and the technical description makes my brain think about this in unfamiliar (hence, uncomfortable) ways does not mean that this is a "bad" UI.
Different paradigms require different solutions.
Edited for incorrect closing of formatting tools. Oops.
Edited 2006-11-28 18:04
Here here! Why does this seem to be lost on so many posters? Clearly they are designing something that not only has technical limitations, but they are designing it for children who may have never even used a computer before. Why shackle them to a UI that even experts agree is flawed? Let them use the device for what it's intended, not to further propagate some company's monopoly or some poster's idea of what the best desktop UI is.
Because whatever OS they move onto after that will use the "normal" pardigm, Gnome, KDE, Windows, OS X, whatever, and they'll fall behind other people in trying to do thier tasks/jobs/assignments until they catch up. Instead of shackling them to a UI that is flawed, you are creating a class of people who don't understand the current and highly relevant UI. It seems like it is designed to hold the target audience back, not help them move ahead
I admire the IDEA of Sugar - to rethink the tired old interface - but I don't really "get it" yet. It doesn't have a metaphorical foundation to build upon.
I tend to think icons organized on the screen (like a crowded desktop) are the way to go, and "minimizing" to *somewhere* on the screen is the most logical way to manage multiple windows. This is a fairly simple way to present a familiar feeling and not completely foreign interface.
"I tend to think icons organized on the screen (like a crowded desktop) are the way to go, and "minimizing" to *somewhere* on the screen is the most logical way to manage multiple windows. This is a fairly simple way to present a familiar feeling and not completely foreign interface."
Yes but this is because this is what we have today that we think this way. We assume that what we have is the best, efficient and most suitable way of organizing.
They aren't trying to present a familiar feel! Not in the slightest. They are creating an intuitive, education-oriented GUI that will be quick to learn and quick to allow full exploration of the device.
New things are always hard on those used to the old.
and also, I don't think that kids are going to be reading through these huge purpose-oriented docs.
For the record, new does not equal better. Just because they are thinking outside the box doesn't mean the new interface is any better or more advanced than the desktop paradigm.
Frankly, I don't see the new interface as "intuitive" AT ALL, and please don't think it's because I'm too stupid to understand that I've been trained on an existing metaphor and it's not my first instinct is too look for like-minded organization. I don't see Sugar as superior, because I don't think anything about it appears to be decipherable without guidelines.
i would much rather see the different "apps" sorted as buttons or tabs, with the desktop being one of them. that way you do not have to minimize all running apps to access the desktop.
but most of all i would like said "tabs" to be task tabs, where in each tab one is working on one specific file or similar object. one object, one tab.
at times you may want to align two tabs side by side to visually compare or reference one while working on the other. this should be allowed. but no free floating windows (one problem here can be the im programs, not for the individual contact communications, but for selecting who to contact).
and if a "app" have to ask the user a question, the question should be attached to the inside of said tab (i kinda like the way firefox and IE does it with the question/warning bar for popups). and if this happens while a tab do not have focus, it should not steal focus, ever.
I admire the IDEA of Sugar - to rethink the tired old interface - but I don't really "get it" yet. It doesn't have a metaphorical foundation to build upon.
I believe the idea behind SUGAR is an interface centered around activities, just like Don Norman advocates:
http://www.jnd.org/dn.mss/human-centered.html
It makes a lot of sense; desktops nowadays focus on discoverability of the controls, which is a good thing in and of itself. However, discoverability of the theoretical model behind the activity sometimes gets obscured, and workflow suffers as a result. And if I read the guidelines, they have the latter in mind, and if I read Thom's rant, he says discoverability of the tools isn't that important.
So no point of contention there actually 
Considering the desktop metaphor is still in it's infancy I'd say burying it is way too soon. Most people make the mistake to judge the desktop metaphor based on the poor insufficient implementations in Windows, OS X, Gnome and KDE.
All of these DE are missing essential elements of the desktop metaphor, elements available in AmigaOS 1.0, OS/2 2.x and in BeOS.
The desktop metaphor is good. It's the main stream implementations that suck.
Oh well... Here's a small list. Mind you that some of these have been fixed in Vista or OS X or Gnome/KDE. But there is still a long way to go. At least they have all understood the importance and relevance of indexing in the Desktop metaphor.
* Proper drag'n'drop printing for one (why does the office suite start when I drag a document to the printer? The Print Manager should just load a "Document Parser" plugin and print the document with no further crap).
* True system wide plugins with clearly defined interface (think translators, available in BeOS/Haiku, Syllable, SkyOS, and datatypes in AmigaOS, MorphOS, AROS).
* natively supported extensibility in all applications (not unlike REXX in OS/2 and AREXX in AmigaOS).
* Extensive usage of File Manager to handle tasks (think template creation and usage in OS/2, Gnome has such a support but it's actually hidden away *sigh*).
* Extensive use of drag'n'drop, drop, point'n'click operations (think font changing or color changing of a window in OS/2).
Firefox and Outlook Express (earlier than v.7 (Windows Mail)) are two good examples of anti-Desktop applications, one might add in Thunderbird, Microsoft Office and OpenOffice (most office suites are generally anti-desktop, due to main stream OS'es having insufficient frameworks in earlier version, requiring the applications to handle OS-tasks).
OTOH, the usage of individual files as internet shortcuts (favorites in Windows) is a good desktop-true solution.
* Proper drag'n'drop printing:
Had that with JazzBench on my Amiga 1000 and 4000. While of limited use without the full print/format code of the original creation program, it sure made things easy when you needed a code dump or a printout of an interesting text message.
* True system wide plugins (datatypes):
Using in BeOS today, Amiga in the past. I can't stand using OSes without datatypes. I like that once a datatype is install *ALL* programs that use that data can now understand it. It is just plain weird using a computer to save a file in one format only to find another program on the same computer can't read that format.
* natively supported extensibility:
Never learned AREXX, used lots of AREXX scripts, the biggest failing of BeOS was not coming with REXX - BASH is no REXX. Worse even the 'HEY' utility is not shipped with BeOS thus limiting the power of scripts. I know lots of people swear by Ruby but whatever the choice all OSes should ship with a scripting language from day one.
* Extensive usage of File Manager:
Do you mean like ClickDOS? If so, then yes!
There are still others, BeOS add-ons seem be very well design. And OpenTracker's find function is way better than Window's. (I have not use OS X lately to compare.)
When I watched that video, it made me think of an overcomplicated version of an old Palm Pilot, which truly is not the way to go. Giving kids a standard flexible desktop is the only way that they will be able to get up to par with the rest of the world, and in some case they will probably surpass many of us
The other issue that I have is that these OLPC laptops have very limited screen real estate, so the idea of throwing big bulky borders and icons around the screen seams as though it may be counterproductive.
Adblock is your friend.
https://addons.mozilla.org/firefox/10/
This interface is certainly - different. However, it is hard for me to judge its effectiveness given that I'm an experienced user of the conventional desktop. That is the paradigm in which I am currently trapped, and thus compare computer interfaces to. How do I know that this interface wouldn't be second nature to someone who has never used a computer before?
I looked at this sugar "masterpiece" and think that if you expect that children who may use it are idiots who don't know how to work with menus then you can jerk off and quit computer business and never look back. Dumb down every application and then leave unbelievable lame design of GTK file open/close dialog... this is beyond me (maybe I am idiot too?).
I am not surprised that Thailand Government sent this project into /dev/null...
Actually Thailand is far from OLPC's "Third World" target, because of the vicinity to Taiwan commercially available $150 laptops might not even be that far in Thai stores.
That said, it's still prohibitively expensive. $5 should be the target if they are really talking "Third World". Of course some governments can surely be corrupted into buying a few million of these MIT laptops for $100.
But if you consider $100 in the "Third World" is food for 10 people for a whole year, I very much doubt any government has the budget for it.
I think this UI might be very successful. I think the kids will love it. The key thing here seems to be using icons without text because of the inherent internationalization of the project itself. Seems like a very wise implementation to me.
If everybody thought "if it ain't broken don't fix it" we'de still be using rocks and knifes untill now... Thinking different and being Bold is something we should encourage, not put down.
So, I think Thom and the other girl (forgot the name) are pretty WRONG in their squared assumptions. As almost always...
The key thing here seems to be using icons without text because of the inherent internationalization of the project itself. Seems like a very wise implementation to me.
Just because, there is no text doesn't mean you will not have internationalization issues. An image may mean different things to different cultures. Colors may be interpreted differently (e.g. black & white for sorrow).
Even though some icons most likely will be understood everywhere, the job of translate the few ones that are not universal may turn out to be just as much job as translating text.
So, my guess is that their use of icons have more to do with the fact that some of the potential users will not yet have learned to write and read, than to lower the costs for translations.
I think this UI might be very successful. I think the kids will love it. The key thing here seems to be using icons without text because of the inherent internationalization of the project itself. Seems like a very wise implementation to me.
I'm sorry but I strongly disagree - I think the exact opposite will happen, "mystery meat navigation" is simply annoying:
http://www.webpagesthatsuck.com/mysterymeatnavigation.html
"I'm sorry but I strongly disagree - I think the exact opposite will happen, "mystery meat navigation" is simply annoying:
http://www.webpagesthatsuck.com/mysterymeatnavigation.html"
I agree 100%, although what is the relevance, to a single web site amongst millions creating a new standard, to a unified interface across multiple applications.
BTW its not a web site, and conventions for web sites have actually evolved quite rapidly, because it has the potential for such a flexible UI.
It's a shame they haven't taken some cues from the UI of RISC OS. These computers have a desktop that is simple, efficient and effective to use.
It has been used by literally millions of school kids of all ages in the past (as they used to be the de-facto educational standard in UK schools), works well on low resolution displays and it still fast and efficient to use for adults.
In fact RISC OS computers would have been ideally suited to provide the basis for this project as they consume very little power, boot from ROM and can use flash for storage. They also come with a suite of basic applications built in and have a large selection of existing educational software.
One company did actually start producing machines for Third World schools that were solar powered and came in locally built rugged wooden cases:-
http://www.explan.co.uk/solo/index.shtml
I don't know what became of that project though.....
I actually don't dislike the idea of rethinking the interface. 99% of the time I use my applications full screen, especially in my 12-inch laptop display. I hate spending so much time moving windows around, trying to get the window size "right," etc. I also like the frame (activated by going to the corners), that seems much the way I actually have my interface set up. I realize it does have its problems but it's good when screens are small. And I can see using this interface without a mouse. Having the support of the MIT I guess they are doing a lot of research on usability.
I agree with Thom, though, that getting a leaner gnome should be a priority for the project and a great contribution for the community as a whole.
I actually don't dislike the idea of rethinking the interface. 99% of the time I use my applications full screen, especially in my 12-inch laptop display.
I think that is a very important point. Most users on small laptop screens seem to prefer maximised windows anyway, so I don't see how a traditional desktop environment could be superior in any possible way. I see Sugar not so much as an attempt to provide a "dumbed down" interface for children, but an attempt to get the maximum out of the capabilities of the hardware (while at the same time providing an interface that is ideally suited to the situation those kids are in).
Thos, you describe in great detail that kids aren't idiots and well capable of learning computer interfaces, yet in the beginning of the article you question just that! I can't really follow that logic.
Neither do I believe that anyone growing up using an OLPC computer would have any trouble switching to another interface concept. Moving windows and clicking desktop icons isn't rocket science after all. The complexity lies in the actual capabilities and those differ from system to system anyway.
I like the idea of not only thinking about the GUI, but the use of the keyboard. The kids are not considered to be stupid because if they would be - what should they need a keyboard for? The keyboard still is the main input method and it's considered to be important in use. Therefore, proper bindings to the GUI are discussed.
The GUI might have the following effect: Kids learn how easy using a computer can be, then, after a few years, they get into school and see the "old fashioned" GUI design. "How boring!" or "Why that complicated?" could be the reactions.
I'm not commenting on the other points, since I don't really follow Mr Negroponte's carer. I don't know if he is aware how things are in these 3rd world countries.
But most of the troubles linux has with hardware are because the vendor doesn't support it, and only has binary drivers for windows. Now, I doubt the first thing anyone will do when they receive an OLPC is switching the sound card and wifi card to something OLPC doesn't support. And I also doubt the people behind OLPC would choose any hardware unsupported by linux. They should be delivered fully configured and ready to work.
I don't know if there won't be any tech problems when the OLPC is delivered to these remote places, but I do know they can reduce or eliminate problems caused by users. I didn't see any cli in the videos, and I doubt you can run "sudo rm -Rf /" on the chat program...
Linux has to do many things for everyone. The OLPC only has one target, and a limited set of functions.
@rakamaka You have obviously, put a lot of effort into your post, but you make the same mistake *I* do which is obscure the points your trying to make. I'll try and ignore the waffle and respond to the points.
1) Mr Negroponte driven by intellectual not financial
2) 3rd World children backward
3) Limited by Small storage, and Display Size(hand cranking I thought had been removed)
4) What happens when something goes wrong.
In response.
1) The harsh reality of the things that would benefit the project, by it being driven by "The Marketplace"
is simply not going to happen for many reasons...The main one being there is not a computer marketplace. Its very monopolistic, Look at the main hardware, and software manufactures.
2) You really need to look at the countries this device is heading for. I just think you have the wrong end of the stick. I don't think you are intentionally being insulting.
3) The device is more powerful than you think. The harsh reality is that software evolves at much slower rate than hardware. The second point is look at what this device is designed for, and how it will be used. I can't think of anything that it needs to run where it needs more anything.
4) This is the only part that I think is interesting. You mistake what the device is, and how it is used. It is the going to be the largest manufacture of any single *hardware* platform ever. Think about the significance of that for moment. Now take a little time and look at what it *does*. Your analogy is soo off base it not comparable. In reality the OS in this instance works more like a Phone, PVR, blackberry, nokia 770
Now you are the one with the Ivory Tower attitude!
Sorry, who do you think were teaching the teachers how to use computers in the late 1970's and early 1980's? Answer, many times it were the students themselves who had no trouble in digging out the details of how the machines worked and spent so many hours with the machines after school till the point that the maintenance staff had to kick them out. I know, I was one of those students. And if computers back then had the mesh networks these babies come with it would had been harder still to get rid of us. Even your analog fails - put a real NASCAR in the auto-shop of any high school and you could not slip a grape into the remain floor space from all the students. And yes, they would be reading all the manuals too!!!
The nature of computers are that you don't have to understand how best to use them for the poorer countries, unlike here in North America some stupid committee might switch to something entirely different next year these people can't afford to dump the lot if they find the software does not match their needs. Instead they 'HOLD ON TO YOUR HAT' ----- REPROGRAM them to fit their needs. Before the big budgets here in Ontario many schools helped to develop and distribute a series of education programs, many of them written by the students themselves. Again don't forget that mesh network, good programs will spread like crazy ie fast.
The rest reads just as dumb to me. Power supplies that don't depend on the grid - makes sense to me! Small displays? I learnt on 40*25 character displays and delivered business software on machines with only 80*25 character displays - since when did display size become so limiting? Only 512MB? Only? Only? Again I delivered A/P and A/R and complete inventory systems on machines with only 32 KBytes of memory, what do you think the child need more for? Oops, pen disk! Even then my comments stand, why would children learning about computers need more for a while. At-least they will learn not to fill it up with junk, people on a memory budget soon learn that they can't have it all, and that they don't need it all either. I would killed for a computer with those features when I was in school in the 1970's (yes I did fight over use of the school's few computers).
Linux - the kids will maintain it themselves just like thousands (millions?) of kids already do today! And how is installing a Mac from a CD any different than installing Linux setup for the laptop in the first place. All the laptops are the same, they all use the same install CD.
Your complaint is silly about installation because there is only one real model, when Amiga, Mac, Atari ST only had one or two models and a lack of different hardware options for particular functions there were also a lack of install problems for their OSes. The problems we see today is caused by the wide range of hardware needed to be supported, not because the software is hard to install.
One model means easy installs!
Edited 2006-11-28 20:44
Agree completely.
Sorry, who do you think were teaching the teachers how to use computers in the late 1970's and early 1980's? Answer, many times it were the students themselves who had no trouble in digging out the details of how the machines worked and spent so many hours with the machines after school till the point that the maintenance staff had to kick them out. I know, I was one of those students. And if computers back then had the mesh networks these babies come with it would had been harder still to get rid of us. Even your analog fails - put a real NASCAR in the auto-shop of any high school and you could not slip a grape into the remain floor space from all the students. And yes, they would be reading all the manuals too!!!
We put Linux thin clients into our elementary schools, full labs of 30 computers (donated P2 333/400 MHz initially, now donated VIA C3 800 MHz). When the labs went in, it was the teachers that had problems with them, not the students. Several schools implemented peer-tutoring programs where the grade 6 & 7 students helped the younger children learn to use the Linux apps. A couple schools had the older students develop pamphlets and booklets for teaching others how to use the apps (all done using the Linux labs). Some schools even had students give workshops for the teachers.
Kids are not idiots, nor are they unwilling to learn.
Having an identical setup for the servers in each school, as well as identical hardware in the labs, made it possible for 2 in-school techs to manage 37 elementary school labs, and for 1 district tech to manage the 37 servers. There's something to be said for minimising choice intelligently.
And having identical hardware means replacing a dead/dying system is as easy as power off, unplug, plug in, power on.
Correct URL
(here are the OLPC screenshots)
http://www.thecodingstudio.com/opensource/linux/screenshots/index.p...
Greetz,
YBK
Why this conservative approach, Thom?
There have been several revolutions in teaching - take maths. Arithmetics alone is not A and O, and neither is geometry. We've had our CLI, and our X-Window. Gosh, we STILL have them around!
But this does not mean it HAS to stay that way. Why not think when using the PC? There is no necessity for input into rectangular boxes (like you and ELQ suggested). Thre is no necessity for output into rectangular boxes (like you, etc.).
It is shocking how unbelievably unflexible some people are. Does it make you proud of yourself or what?
Getting back to the OLPC Human Interface Guidelines, I have found them easy to grok and easy to follow. Just have a look at the pics if you cannot follow the text. Than THINK like you wanted to say something, draw or write something, get or give something. Good luck!
Greetz,
YBK
I was reading something on digg the other day, about innovation that has come from OSS.
This really is a step beyond ribbon bars.
Ignoring the interface for a moment. The OLPC has a pretty unique keyboard, and there were two things that struck me.
1) Group working buttons. OMG they have built a social device. Computing as a group experience. I cannot imagine a greater idea that has come from this project.
2) Slider buttons. Now this I really like. It makes so much sense in the world of guages. The keyboard is bad for lots of things and replacing a knob is something it has never done well.
Sorry the interface what it should be about. I noticed several things
1) Symbols representing actions. Now this is wow. I have never seen it done, and I am a little surprised it has been in todays highly detailed, animated world. I do think its a great idea but there does seem an awful lot of them to learn.
2) Screen clutter. I'm a strong believer in having as little on the screen as possible, but this really does take the thing to the other end of the spectrum. Having recently looked at old desktop analogies working on *low resolution* monitors. I have to say its a step in the right direction because its not a big screen.
3) Greys and Blacks. Its like a black and white TV. I had all but forgotten that the screen runs like this to preseve power, and be more visible under bright light.
Never have I seen anything soo ugly ever. I can see that almost every decision is well thought out, and there is a damn good reason for it. Its not a bad document at all. I cannot comment what its really like to use, but its obvious why they have made the choices they have. What surprises me is how much time they have spent making the whole thing functional, rather than spending time on making it *attractive*. I can see the limitations, but look at what has been achieved with the original gameboy that had greater limitations.
I think the interface of the OLPC was lots of good ideas, with *sound* logic behind those choices, and I hope many of these Ideas filter back through to *MY* desktop. I think people here are forgetting the *purpose* and *limitations* of this device. Its definitely a project to watch.
The interface does not have the luxury of several years of little tweaks it has to evolve rapidly, or be scrapped for a more traditional approach.
Thom: "I just read through the human interface guidelines for the project; and by god, I got lost after only a few paragraphs. How are kids supposed to learn all this?"
It's a HIG for developers, not a user manual for kids. Strawman argument. (FWIW, I understood it just fine, and I'm no great shakes as a programmer.)
"However, more and more I am getting the feeling they are just doing this for the sake of doing it; not because it is an inherently better way of teaching kids computers."
They aren't doing it to teach kids *computers*. The computer's just a means to an end, not the end in itself. (Something that nerds and geeks, bless 'em, sometimes forget about.)
"Our desktop paradigm may have its shortcomings, but it does have one major advantage: it is tried and tested ... and everybody uses it."
Two very, very important words for you: ubiquitous collaboration.
The key concept is that networked users should be able to work together on joint projects, and the whole OLPC OS is completely designed to facilitate this. Interaction is direct, immediate and flexible. Multiple users can work on a single document, and discuss what they're doing at the same time.
The traditional Mac/Windows/Linux GUI, on the other hand, is completely designed around the one-user-to-one-desktop approach set down in the early 80s by the original single-user Mac OS. Users traditionally collaborate via dedicated special-purpose applications - email clients, irc clients, ftp clients, etc. - indirect, laggish and each slaved to its own narrow domain. Instead of merely being a means to an end, the network protocols have effectively been treated as the end in itself.
So the OLPC crowd could wait another five-to-ten years for the traditional desktop OSes to layer on some tolerable collaboration support. (e.g. We're just starting to see this now with applications like SubEthaEdit.) Then add as many years again for all the different implementations and user interaction models that have sprung up independently in that time to consolidate into some kind of ersatz 'standard'. Or they could just skip all that crud and get straight to the point right now.
...
Anyway, there's nothing fundamentally new here that I can see - it seems to be drawing on HCI research done over the 70s to 90s. (Unlike the traditional OSes, whose interaction models date from the 1950s to 70s.) And it all makes very good sense when viewed from the 'collaboration everywhere' perspective:
- Zooming desktop (c/o Raskin) whose root is a wide view of the local network space displaying other users with whom the user can choose to interact.
- Document-centric model (c/o Apple and others) ideally suited to supporting granular, task-oriented interaction from the ground-up (VNC's as subtle as a head-punch compared to this).
- Automatic ongoing persistence of data (Gelernter, PARC, etc, etc) that avoids tedious manual filesystem housekeeping (which distracts from the actual work) and alleviates the fear of making individual or collaborative changes (since undo-by-reversion is always available).
And other things, like the full-screen, single task interface (which also maximises use of the very limited 7.5" screen) make sense too. That single-task UI will be rather more powerful than you might think, btw, thanks to the ever-present collaboration tools. No constant switching back-n-forth between MS Paint and Messenger, or MS Word and Outlook needed here, since editing and communication are both done in-situ.
...
Mac/Windows/Linux all expend a ghastly huge amount of the user's time following a whole bunch of baroque, ancient rituals on the way to actually getting useful work done. Ironically, they don't have a whole lot of choice here, since they have to keep a huge established base of existing users happy - and if there's one thing that users hate, it's any sort of change from what they're used to. They may not object to incremental change that merely builds upon everything they already know, but any sort of radical departure that requires them to throw out all their existing knowledge and start over again from scratch will inevitably receive the bums rush PDQ.
OLPC, OTOH, doesn't have an established user base, so it can afford the luxury of a clean-slate approach that skips the ancient practices and leverages much more recent research and technologies. It's all about putting users first, and the computer firmly back in its place as a mere tool - the means to an end, not the end in itself.
So good on OLPC for being so bold as to cast off some of the historical deadweight for a change, instead of carting it along ad-infinitum like everybody else. And if this puts the wind up the conservative tech establishment in the process, that's hopefully a sign that they're doing something right. 
I've seen interfaces like Sugar used elsewhere, and they've been used primarily with persons with cognitive issues, and in attempts to communicate with animals (dolphins, gorillas, etc.).
I think that the interface was designed by cognitive scientists, not computer professionals, for children. Keep in mind that things like the "desktop metaphor" are completely wasted on people that have never dealt with the real thing. You are targetting children, from a broad spectrum of cultures, that can't read or write yet (well, not all of them can).
As an educational tool, the OLPC has to first and foremost present an abstraction of the world that children find inviting and can relate to (more or less).
I agree that the interface is not practical for how I work with a computer, but my 4 year-old would likely have a different opinion and he'd be right (for what he's likely to use the computer for). There's plenty of time to spring the desktop paradigm on kids, and the OLPC computers will still be able to do that when the kids reach the stage where that makes sense.
I think it's ridiculous to pan it because it doesn't look or work like you are used to, because that would make it inaccessible to the target audience.
From the first paragraphs:
<quote>
it represents an intrinsic quality of the learning experience we hope the children will have when using the laptop
</quote>
This is what happens when you pretend to be giving "the answer" to the world's problems (and being smart enough to get some governments believe it) instead of doing real business.
I am one of those who think this project ought not to succeed for being **utterly** patronizing (and --in my belief-- utterly useless: the children need water + soap + true education (reading-writing) + PLOUGHS )
However, let the people decide.
Seems like you live in a dichotomy world. Where a country, city or school is either reasonably affluent, or cannot afford "soap and water".
There are less affluent countries that have cities. And schools. They have food and water, and even soap!
For these places, a tool like this may be useful. This OLPC project is targeting a specific narrow range of users. People in countries that aren't absolutely starving to death. These units aren't replacing any other sort of foreign aid. There is no condition to stop grain or medical shipments to countries where OLPC is going.
Please think of the world as a spectrum encompassing varying needs. This is a tool that will meet some of those needs.
"the children need water + soap + true education (reading-writing) + PLOUGHS"
You mean, just enough that Spain (and the rest of Europe, America etc) will be relieved of the tiresome burden of handing out food, but not enough to actually threaten our economic domination?
Nice self-preservation thinking, there.
You, like many others, miss the point of the OLPC. The OLPC is not going to people in Rawanda(?) instead of food and sanitation aid. This is going to people that already have a schooling system, not to mention sanitation and housing.
Don't be so niave as to think that the OLPC is a replacement for 3rd world aid and support for poverty-stricken nations. The OLPC serves a completely different purpose for a completely different mass of people. If you don't realise that, then perhaps you need a teaching-aid.






