[IAEP] For Sugar Everywhere, Google-ize!

[Nicholas Doiron]

This is a tremendously interesting but increasingly technical discussion. 
It's difficult to weigh pros and cons of an entire OS in an e-mail
discussion. Would it be possible for people to create pages on the wiki so
we can get a clearer outline of:

* What is each OS?  Explain to a teacher using SoaS what ChromeOS and
Android actually are. Avoiding conflation with Chrome browser and Droid
phone.

* What education apps exist already?  Are there grants or challenge prizes
for app developers?

* Do you believe Sugar activities can make the transition?  Will Native
Development Kit (Android) and Native Client (ChromeOS) help?

Thanks,
Nick Doiron

On Thu, February 17, 2011 9:49 am, Martin Langhoff wrote:
> On Wed, Feb 16, 2011 at 10:32 PM, C. Scott Ananian <cscott at cscott.net>
> wrote:
>
>> This seems to me to be a red herring.  What does connectivity have to
>> do with your choice of OS?
>
> While technically possible to write all sort of sw yourself, you
> choose an OS based on the affordances it offers.
>
> The OSs being discussed (Android, ChromeOS) have very strong
> assumptions about ubiquitous connectivity to the internet and the role of
> the device (network client, not peer, not server).
>
> With enough work and time you may be able to provide all the missing
> bits and fix the broken libraries and APIs. You might even rewrite the apps
> in the app store to work without connectivity.
>
>
>
>
> m --
>  martin.langhoff at gmail.com
>  martin at laptop.org -- Software Architect - OLPC
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
>
>