The problem is that you are thinking of it as a general-purpose computer rather than an appliance.

Look at it this way- I go to Best Buy and purchase a particular model of wireless router; it is version 'n' of the hardware and runs a Linux core. The next week, I go to Staples and purchase another of the exact same brand and model of router, only to receive version 'n+1' which now runs VxWorks. Both meet the same functional specifications as outlined on the package and both have the same configuration GUI. Nowhere was I guaranteed that I would get a Linux-based router.

Its the same here. Each Africa may have different internal hardware, but that is all hidden by running different ports of the same OS and applications and only guaranteeing the same minimal functional level. The issue comes when a power user decides to move beyond the installed functionality by adding a software package which is not available for the archtecture of his specific Africa (ever try to find modern CE software for anything other than ARM?), but this is not the target audience of the device.

I'm reminded a bit of the classic WB cartoon where the elves describe mass production to the shoemaker. What people couldn't foresee what the idea of transportation becoming so cheap (or labor remaining so expensive) that you could actually make the product half-way around the world and still sell it cheaper than if you made it in the US.

Similarly, the 1960's cartoon "The Jetsons" envisioned a future with a 3-day work week, most of which involved having to periodically push "the button". By the 1980s, though, we began to see new office technologies such as the fax machine not as the means to decreasing work, but as the means of expanding the work day to having more time to do the same work. The same can be said or the Blackberry which provides such a level of connectivity that one never has to let an employee "stop" working for the day.