Skip to main content

PyCon: Keynote: One Laptop Per Child

Here's an outline of his talk on the One Laptop Per Child (OLPC) project:
  • Formal education is bad unless you have great teachers.
  • There are a billion school age children in third world countries.
  • They created a next generation LCD screen. Monochrome at high resolution. Color at lower resolution. Sunlight viewable.
  • Laptop has very, very low power consumption: 1 watt.
  • 20 hours of battery life.
  • Automatic mesh networking.
  • Automatic routing for other laptops.
  • They had to get rid of the crank because it was fatiguing the laptop.
  • Many ways to power it including a separate pull chord.
  • All sorts of incredible innovations.
  • No moving parts.
  • Custom filesystem for the flash drive.
  • Wireless range is 2km.
  • Based on Fedora Linux.
  • Completely new user interface paradigms.
  • Great paradox of open source: it's too hard to figure out how to hack on it.
  • Hence, they added a "view source" button and coded almost everything in Python. This is my dream come true!
  • Help them out at dev.laptop.org.
  • $100 price range, but you can't buy one yet.
  • They're planning on rolling out 1-10 million units next year.
  • I tried it out, and it's amazingly cool!
  • OLPC is looking for volunteers, especially to write apps.
  • Contribute significantly, and they'll give you a laptop.
  • "Ideas are dangerous."
  • Get an emulator at wiki.laptop.org.

Comments

Unknown said…
Why this is a really dumb idea.
-------------------------------


1. Much of the world's children have more pressing needs, such as proper nutrition. Without proper nutrition learning is impossible. You can't eat these things.

2. For what these laptops cost you could buy a traditional set of books that you can a) write in, b) refer to without power, and c) don't break.

3. Think of the most-base thing these laptops could be employed as by a group of adults. That's where the will ultimately end up. Hm, ad-hoc networked communication and a battery... what a wonderful thing for a terrorist cell...

4. If the don't end up used as above, they will end up as a) toys, b) blocks, or c) shovels.

5. The batteries and other compounds contained in it that are toxic and should be "disposed of properly", won't be.

6. A computer is a tool for the mind. You must already know basic math, reading, and writing to even begin to use it effectively. But most importantly, you must have a mind. These engineers obviously think that the rest of the world thinks like they do.

7. The vast majority of people in the world are not the least bit interested in the source code.

8. The goals they have can be met in better, cheaper, and more environmentally friendly ways.

9. A laptop for a child is only good for a self-starter. That trait is actually rare, worldwide. The first-world got where it is by working hard and working smart, and, yes, by exploiting others to a large degree. Even now, the worlds poorest children are often put to labor. Giving them a laptop will be meaningless to them. Using the money for these laptops to stop exploitation from large Western corporations would be more effective. The laptops would only add to that. Where do you think the raw material and labor will come from to make these things?

Ultimately, this is just a "feel-good" project for people. But Somalia has a lesson: it's that even good intentions rarely work. The "war on poverty" has been going on for decades now. It's as bad as ever.


However, I do agree that formal education is pretty bad, even in the USA. We should fix our own problems first.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p