<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
Eli Marmor wrote:
<blockquote cite="mid:4A9A2054.FC80910@netmask.it" type="cite">
<pre wrap="">Hetz Ben Hamo wrote:
</pre>
<blockquote type="cite">
<pre wrap="">...
Will it be totally open? I don't think so because they have to support
their DRM'd music/video which you buy, and their DRM is from ..
Microsoft, but OTOH writing/porting an app to N900, is IMHO way easier
then to Android/WebOS/iPhone.
</pre>
</blockquote>
<pre wrap=""><!----> ^^^^^^^^^^^^^^^^^^^^
</pre>
<blockquote type="cite">
<pre wrap="">...
</pre>
</blockquote>
<pre wrap=""><!---->
By the way, don't forget that:
1. Android is Linux.
2. WebOS is Linux (Palm left their proprietary OS).
3. iPhone is BSD.
4. ...and not only Nokia's Maemo is Linux/UNIX based....
</pre>
</blockquote>
While technically true, it is also totally irrelevant.<br>
<br>
When you write a phone application, you rarely interact with the
kernel. Your main interaction is with the GUI. As such, which are the
toolkits and what languages can you use:<br>
Neo: C/C++/Python/Anything. GUI is ETK, GTK, QT, wxWidgets or whatever.<br>
WebOS: I don't know what language (C?). GUI is Palm OS<br>
iPhone: I don't know what language (Objective C?). GUI is iPhone<br>
Android: Java. GUI is Android<br>
Windows Mobile: C, GUI is Win32ish<br>
Nokia: C/C++. GUI is QT.<br>
<br>
Of this list, only the first and the last provide you with a
development environment that is the same for the phone and for you (or,
at least, my) desktop. In some cases I literally run the same software
on my laptop and on the phone.<br>
<br>
With Windows mobile, the framework is somewhat the same (but it is a
horrendous framework to develop desktop applications with, and it's
even worse for phones).<br>
<br>
Then again, after spending the past two months doing Android
development, there are also advantages. On the Neo, by far the best
environment to actually send and receive phone calls is QTopia, which
specifically deviates from the "standard your desktop is running". I
have two SIMs connected to one number. With most environments, my
"dumb" phone would ring first. The exceptions were QTopia (if the phone
was not asleep while the phone call came) and the Android device, both
would actually ring before my dumb phone would.<br>
<br>
In all honesty, I would rather have a phone that works than have a
phone that runs my applications. I am much more worried about Android's
lack of friendliness to third party applications (unless they come
through the Market) than I am about the fact it is running a
non-standard environment. I am sad to say that, in that respect,
Windows Mobile is better.<br>
<br>
Shachar<br>
<pre class="moz-signature" cols="72">--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
<a class="moz-txt-link-freetext" href="http://www.lingnu.com">http://www.lingnu.com</a>
</pre>
</body>
</html>