[Mep-dev] Tuesday Challenge for 14 April 2009

[Assi Friedman]

I find it a bit strange to try and justify a solution by explaining why not
to go with it.
But here is one. As far as Android, I would be weary of fad widgets that
spread like wildfire just because it comes out of a fad generating
corporation such as Google. Case in point, does anyone remember the
Handspring Visor Springboard and the firestorm the ensued?  I seem to
remember statements such as "open standard for years to come..." Does anyone
know where it's at today? Android definitely uses all the correct buzzwords,
but will it really be there? What is your risk tolerance? Since it's a
hobby, it's probably pretty high.
Assi KK7KX


> -----Original Message-----
> From: mep-dev-bounces at uppermeadow.com [mailto:mep-dev-
> bounces at uppermeadow.com] On Behalf Of Michelle
> Sent: Tuesday, April 14, 2009 10:00 AM
> To: mep
> Subject: [Mep-dev] Tuesday Challenge for 14 April 2009
> 
> 
> I'm interested in reasons *not* to select Android as a baseline OS for
> MEP stations.
> 
> Here are a few more details:
> 
> Android is an open-source operating system primarily intended for
> cellular phones.
> 
> www.android.com
> 
> Android scales to systems like MEP, third party development is
> encouraged, it's supported by a consortium of all sorts of people we've
> heard of (http://www.openhandsetalliance.com/), and it uses lots of
> linux-like process protection protocols that would seem to enhance
> stability and usefulness. People seem interested in developing for
> Android, and it might help MEP greatly to go in this direction. What do
> you all think?
> 
> I have an image for the TI OMAP from the Embedded Systems Conference,
> and would love to hear from anyone else pro or con on Android.
> 
> _______________________________________________
> Mep-dev mailing list
> Mep-dev at uppermeadow.com
> http://uppermeadow.com/mailman/listinfo/mep-dev