Commentary

Serdar Yegulalp
 

Symbian: As Open As They Wanna Be (But How Much Is That?)

What with Google's Android currently stuck in the state of a work-in-progress, it was only a matter of time before someone else ponied up their own open source competition for the smartphone/handset market. But it isn't some newly-minted firm flush with a round of startup funding -- it's Nokia's own Symbian, to be merged with the S60, UIQ, and MOAP(S) platforms into one great big happy open source mashup. Well, that's the theory, anyway.

What with Google's Android currently stuck in the state of a work-in-progress, it was only a matter of time before someone else ponied up their own open source competition for the smartphone/handset market. But it isn't some newly-minted firm flush with a round of startup funding -- it's Nokia's own Symbian, to be merged with the S60, UIQ, and MOAP(S) platforms into one great big happy open source mashup. Well, that's the theory, anyway.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

We can put aside the fact that nothing will appear, even on paper, until well into next year. By that time the first Android handsets are likely to be out, even if they're still first-generation models designed more to hook early adopters than the broad swath of consumers. No matter: the intent is what matters, and the intent is to liberate Symbian from its proprietary roots and make it something that can be contributed to and derived from freely.

Again -- that's the theory. What strikes me first of all is that we are not just talking about one platform being opened, but several -- with pieces from each being merged into a whole. Small wonder we're not going to see anything solid with this until '09, since the Symbian Foundation (the new partnership between Nokia and basically everyone who's not Microsoft or Google) has to figure out exactly how all the pieces fit together. After Sun's hassles with opening Java, for instance, I don't believe for a minute that anyone can simply wave a Proprietary-to-GPL Wand and make the magic happen by fiat.

That would certainly explain the choice of licensing. Symbian's elected to use the non-GPL-compatible Eclipse Public License -- probably because it allows those who submit code to an EPL project to keep those submissions proprietary. Android's use of the Apache Software License is of the same flavor, and was probably adopted for the same reasons: so that folks who have technologies that give them competitive advantages won't feel like they're being told to surrender all that. The big difference, however, is that the ASL is compatible with at least one flavor of the GPL (version 3). Eclipse is not, and that right there sends a message as to what sort of crowd the "new" Symbian is meant to attract.

What I see mattering most with any open device initiative -- whether Google's or Nokia's or what have you -- is what kind of community is involved, and how the members are expected to contribute. A community that is more corporate-centric than truly developer-centric is going to stay corporate. Nokia is doing this primarily as a pre-emptive strike against Google (and Microsoft), to preserve turf that it fears will be eroded by both open source and proprietary solutions. So if there's a community here, it's one of industry partners and not guys at keyboards.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links