Language Selection

English French German Italian Portuguese Spanish

Negroponte: XO-1.75 goes ARM, XO-2 is canceled

Filed under

This morning I woke up to find an e-mail in my inbox which contained a link to an interview with Nicholas Negroponte. While reading it over breakfast I managed to spill my tea because I couldn't believe I was really seeing the words I was looking at. XO-2 development canceled? An XO-1.75 to replace it? Talk about an XO-3? Going from OLPC to olpc? But let's take it step by step, shall we...

From XO-2 to XO-1.75 to XO-3

NN: 2.0 has been replaced by two things: 1) model 1.75, same industrial design but an ARM inside, 2) model 3.0, totally different industrial design, more like a sheet of paper.

Now there's something I didn't see coming! While I never believed that the XO-2 had gotten much beyond the concept stage I always considered it to be a strong vision of where OLPC was going in terms of device design. Sure, both the hardware and the software for an XO-2 are massive undertakings which would probably overstretch OLPC's limited resources but then again that's what everyone thought of the XO-1 design as well and arguably they did a great job there.

An ARM based XO-1.75 on the other hand is much more of an evolutionary rather than a revolutionary step into the future.

From OLPC to olpc

More in Tux Machines

Today in Techrights

A few thoughts on OpenBSD 5.8

I've been using OpenBSD since way back at release 2.3 in 1998, so I've gone through upgrades that took a fair amount of work due to incompatible changes, like the switch from ipf to pf for host firewalling or the change to ELF binaries. The upgrade from 5.7 to 5.8 was a pretty smooth and easy one, for the most part. The two most painful changes for me were the replacement of sudo with doas and the dropping of support in the rc.conf for the pf_rules variable. While sudo is still available as a package, I like the idea of reducing attack surface with a simpler program, so I made the switch. The two things I miss most about sudo are the ability to authenticate for a period of time and the ability to have a single config file across a whole set of servers. The former I'm just living with, the latter I've adjusted to by having a single config file that has lines commented out depending on which server it's on. I did have one moment of concern about the quality of doas when it incorrectly reported the line number on which I had a syntax error in the config file--fortunately, this was just a failure to increment the line count on continuation lines (ending with a "\") which is fixed in the -current release. Read more

10 recently open-sourced products from big tech companies

Releasing internal products to the open-source community is the hip new thing for technology giants to do Read more