Slashdot Mirror


In the Face of Android, Why Should Nokia Stick With MeeGo?

GMGruman writes "In September, Symbian 3 was Nokia's latest great hope for becoming relevant in the modern smartphone market. Now comes word that the Symbian Foundation is shutting down, ending the Symbian 3 and Symbian 4 efforts. Nokia is now banking on MeeGo, a collaboration with Intel whose release date — and fit to smartphones — is highly uncertain. InfoWorld's Ted Samson thinks that it's time for Nokia to swallow its pride and stop pretending it will ship MeeGo in time to matter, and instead consider adopting Android — or even Windows Phone 7, which after all might finally support copy and paste by the time Nokia decides to hitch its mobile wagon to a new horse."

336 comments

  1. maybe by dropadrop · · Score: 5, Insightful

    I would imagine Nokia feels ditching their own OS would just make them hardware manufacturers, not so different from a large portion of their competition. Add to this that in a certain sense Google has probably partially made Android to ensure that no one manufacturer has a dominating position in the mobile market, and Nokia will suffer from that (Google can ensure products follow standards better when there are a lot of small players vs. one big one).

    1. Re:maybe by Anonymous Coward · · Score: 0

      Plus they'd have to write off all the money the've spent on branding, e.g. the avertising jingle: http://www.youtube.com/watch?v=ocsOIYYedV8

      I think they're onto a winner, and that's not just because I've been replaced by fungio from yuggoth. Okay, maybe it is just that.

    2. Re:maybe by Anonymous Coward · · Score: 0

      going android or windows means being google or microsofts bitch. You become an irrelevant box shifter. Meego is just linux . It gives them control and opens the phone market .

    3. Re:maybe by rtfa-troll · · Score: 5, Insightful

      I think it's more than that. For example, Nokia is Europe based; it has a strong respect for the privacy of it's customers through not gathering data which doesn't really fit directly into Google's way of doing things. Note; I'm not saying that Google lacks respect, just that they do it from a completely different base. They assume they own your data and then voluntarily give you back most of your privacy (compare with e.g. Facebook which just doesn't bother to give you back your privacy.. "Deal with it Bitch"). Nokia has to start from a base of asking for permission to data which they assume you own. I think that in a Google led environment would strongly disadvantage Nokia compared to other companies which would be happy to gather all their customers data and/or hand it over to Google. Adroid was never designed to work for Nokia and there are probably plenty of other things like that which just won't be a good fit.

      Also, if you think that Google is a big target for Java patent attacks that's nothing to Nokia. Nokia almost certainly already has agreements in place that it would be breaking by delivering a java execution environment which isn't compliant to Oracle's spec etc. etc.

      Nokia could go with Android, but only if Google agreed to give them a serious level of long term influence over the platform. That's not something I guess Google would do and it's probably not something Google should do.

      Nokia needs to do something it hasn't had the guts for for years; commit to Meego; promise that Meego will be available for at least seven years, no matter what market success it has for the first couple of years; limit Symbian to the low end; be clear about where it's going; have a vision of a bigger market and see that it's mobile expertise will only be relevant if it can apply them to devices which have the same level of flexibility as a general computer. Commit to delivering low cost Meego devices soon. Make sure that Meego will be available on all pre-existing N700/N800/N900 devices so that there is a guaranteed base market from the very beginning. Even better; if possible provide a Meego upgrade for N97 and above devices. Build up a developer "eco-system" and make sure that you look after it. This will mean that people will be able to believe in the future of Meego.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    4. Re:maybe by RichiH · · Score: 4, Interesting

      > Google can ensure products follow standards better

      Pray tell me: Whose standards will those products follow once there is only one mobile OS that matters?

    5. Re:maybe by digitalchinky · · Score: 4, Informative

      You don't quite know the reality of privacy, Nokia, and asking. These days they don't ask. They make it compulsory. While they may not openly use the data they collect in ways that are immediately obvious, they absolutely do collect data that most would consider even more private than the stuff they hand over to google.

      One Word (okay technically two) "MyNokia" - on Symbian and Maemo handsets the OS forces you to send a text message back to Nokia the first time you turn it on - the payload - IMEI and a bunch of other handset specific information. The Maemo community reacted quite badly to this - The response from Nokia was to suck it up because everyone loves to sell their soul in return for daily text spam.

      Android already runs on the N900, a few rough edges, but it's almost good enough to use as a replacement OS.

      MeeGo - everyone forgets about Maemo - it exists right now, it is good. MeeGo is an arse about face rewrite to fit somewhere between Android and iOS. Obviously Nokia was a little bit smug and now has to play catchup for a few years. It's not like the writing wasn't on the wall though.

    6. Re:maybe by Culture20 · · Score: 1

      I think it's more than that. For example, Nokia is Europe based

      More than that; they're from Linus' country. Linux is like the national operating system kernel.

    7. Re:maybe by Anonymous Coward · · Score: 0

      You're right, but these competitors are making bumper profits and Nokia isn't. So they'd better make up their minds fast since it's no use peddling an operating system no one wants on their phones. Soon Samsung will bring out dirt-cheap Bada OS phones which may be the dark horse winning the race in terms of sheer units shipped.

    8. Re:maybe by rtfa-troll · · Score: 1

      Hmm. Nasty. I wonder why I've never seen this on my N900... Not that it really changes anything. The legal arguments still apply (they ask you permission for your data; have to keep it themselves; can't share it randomly and have to let you opt out). Forcing the mobile owner to send an SMS with personal data in order to use the phone just makes Nokia's recently fired management look sick. They would never have done this in the past and hopefully the new management will allow some level of ethics back into the company. I'll have to add this to my list of warnings I give anyone who asks me if I like the N900.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    9. Re:maybe by frisket · · Score: 3, Insightful

      I would imagine Nokia feels ditching their own OS would just make them hardware manufacturers, not so different from a large portion of their competition.

      That's certainly possible, but this goes beyond Symbian and MeeGo. There is the whole fiasco which was Maemo.

      With the N700 and N800, Nokia had the foundation for a viable, sustainable, open platform for the development of pocket computing, to which they could have added phone capability. Very little needed fixing (mainly the webcam, for which there was never any software except Nokia's own webchat, which no-one used). Instead, they failed to recognise the market, ignored the users completely, and came out with the N900, which was a phone with a hobbled PDA platform.

      To be fair, Google made similar mistakes with Android, releasing 1.* with no support for two key elements, principally Bluetooth and Wifi Proxies. But these appear to be partially fixed in 2.*, whereas the N900 was just an expensive not-very-smart-phone.

      Every time the deficiencies of Nokia's vision come up, their developers (who are excellent people) come up with the same scripted blather about how important the company's marketing strategy is, and how they know best, and how the market for "tablets" is so important. Of course it is, as the iPad showed, but the N800 was there long before, and had more facilities than the iPad, and could easily have been developed into a larger, competitive device.

      But Nokia is at heart still just a phone manufacturer, and they lack the vision to see where the handheld market is going, despite having it explained to them numerous times in words that even marketing 'droids can understand. The future isn't in "tablets" but in portable computing. Call them "tablets" if it makes you feel warm and fuzzy, but don't think for a moment that they are phones with a PDA bolted on. They're computers, and the way to sell them is to make sure they run stuff — simply, easily, quickly, and openly.

    10. Re:maybe by Anonymous Coward · · Score: 5, Informative

      This is wrong. I have an N900 and it's entirely voluntary to register with MyNokia. There is even an application available for N900 to disable/block the entire MyNokia feature. I know because I have it installed :)

    11. Re:maybe by Bill_the_Engineer · · Score: 4, Insightful

      Excellent point. I wish I could mod you up.

      Whose standards will those products follow once there is only one mobile OS that matters?

      Easy! Google's of course.

      Just like Microsoft gave us standard's... I can't finish the sentence.

      From what I see, standards are not very high in Google's agenda. Dalvik the non-standard bastard step-child of Java, and Flash the proprietary home-run of Adobe's are what I see as talking points for Android. Not that HTML5 isn't a priority for Google.

      Of course standards are what companies use until they reach a dominate position, then they become the de facto standard.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    12. Re:maybe by Anonymous Coward · · Score: 0

      >Make sure that Meego will be available on all pre-existing N700/N800/N900 devices

      Yep, they've said MeeGo will dual boot in N900!

    13. Re:maybe by Bill_the_Engineer · · Score: 2, Informative

      My point was competition keeps everybody in check. I not particularly happy with the wording in the parent quote.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    14. Re:maybe by Anonymous Coward · · Score: 5, Informative

      I work for NOKIA and Google is our primary competitor; not Motorola, HTC, Samsung etc.

      We are moving towards becoming an Internet services provider with smartphones playing an important role in this transition. MeeGo plays vital role in this strategy. Qt should allow seamless integration of applications in both Symbian and MeeGo; Symbian is still useful for middle-end devices, MeeGo aims to be the top dog. Qt should allow you to get the same UI experience on both platforms later.

      At this moment we are deploying distributed architecture comparable to Google's so that we can compete in latency and scalability of all our services once the initial pains are over. MeeGo should be fully integrated with this framework.

      Symbian is a nice OS with outdated GUI which shoots it down; MeeGo should be our response to UI; for that we hired WebOS UI designers to help us get there.

      If you ever tried N900 you can imagine what kind of phone would be the first MeeGo phone - you'd be able to run xterm, gcc or most Linux applications on your phone directly - I am not aware of any other phone on the market capable of doing this. Couple this with a capacitive touchscreen, multitouch, UI similar to WebOS yet with NOKIA style, fully offline 3D navigation, microSD, HDMI, hi-res cameras and many more - you can perhaps ditch your netbook and camera and carry only this phone.

    15. Re:maybe by duguk · · Score: 4, Insightful

      Android already runs on the N900, a few rough edges, but it's almost good enough to use as a replacement OS.

      If you're only looking to use basic functionality, (ignoring the stuff unsupported in Android). Meego and Maemo are both vastly superior in the functionality for expert users.

      It's like comparing Windows to Linux; Windows is easier for the general populace, Linux is for those who know what they want. They're really not comparable.

      I suggest the following change to the headline: "In the Face of Windows, Why Should Linus Stick With Linux?"

      What the hell ever happened to choice being a good thing, anyway?

    16. Re:maybe by RichiH · · Score: 1

      In that case, sorry. Yet, I replied to how I read what you wrote.

    17. Re:maybe by RichiH · · Score: 1

      Gah, disregard my parent. I glitched a line.

    18. Re:maybe by CarpetShark · · Score: 1

      "I would imagine Nokia feels ditching their own OS would just make them hardware manufacturers"

      They've been hopeless at supporting Maemo as a software platform, so this isn't something they can currently claim with any integrity anyway.

      On the hardware side, what Nokia should do is try to make the best android phones possible.

      On the software side, they should put a ton of resources into Qt, making it the most desirable development platform for Android, iPhone, Mac, Windows, and Linux. Few companies are in a position to offer that, and it could well be a killer product for them that even Google / Android couldn't compete with. Qt's had two decades of development in it by now.

    19. Re:maybe by dalesc · · Score: 1

      Nokia's respect for the privacy of its (not it's) customers doesn't extend to allowing you to unsubscribe from their annoying mailing lists. I made the mistake of registering when I had an N95. That went a long time ago but efforts to opt out of mailshots are completely ignored. I don't just get emails but SMSs too. I deleted my Ovi account but they continue to pester me.

    20. Re:maybe by DerPflanz · · Score: 2, Informative

      Android already runs on the N900, a few rough edges, but it's almost good enough to use as a replacement OS.

      From the Nitdroid FAQ: "Phone is working too but there is no sound yet."

      I do not know what you call 'a few rough edges', but phone support without sound is a big fat NO to me.

      --
      -- The Internet is a too slow way of doing things, you'd never do without it.
    21. Re:maybe by Richard_J_N · · Score: 1

      Also, if Nokia really wants to succeed, it has to make the *entire* platform open, rather than 3/4 open with all the interesting bits closed. I bought an N900, and it was a delight to develop for, particularly because it has the good sense to run X-windows, so standard Linux apps can easily be ported (even X-forwarding over SSH worked!). BUT there was a killer bug(*) with the camera, which I couldn't fix, since the autofocus algorithm was only available to the binary-blobs. As a result, we didn't buy 400 of them.

      (*)Specifically, you can't use the camera while in the middle of a phone-call, because the camera wants to make a shutter-release noise, but the sound interface is locked because the phone is using it. The simple workaround of taking the photo without a shutter-release click couldn't be done because Nokia wouldn't release the source. I think they fixed it now, but months too late for me. Even more ridiculous was the fact that they did support using the camera in your own software...but only if you didn't want it to have autofocus!

    22. Re:maybe by portalcake625 · · Score: 1

      Got MyNokia on my N95 after updating to v35. Biggest WTF moment in my life. What you do is press the red "hang up call" button (which is also "pause app and gb2standby" in Symbian), reboot phone. MyNokia will prolly ask you again. There'll be an option "No thanks" (or somethng like that). Still friggin annoying, and stupid. Same on the n900, but I did uninstall it.

    23. Re:maybe by Rexdude · · Score: 2, Interesting

      MyNokia is a voluntary, free SMS service that sends you tips and tricks on using your phone. In India receiving SMS is free, so it's not like we're being forced to pay to read them. The service is enabled by default when you purchase a new phone, but you can turn it off and won't be bothered again. I bought my N8 a couple of weeks ago- when I inserted my SIM card and booted up the phone, it greeted me with my Ovi account username and asked to enter my password to enable the Ovi services on the phone. It registers the phone number and IMEI with Nokia, (who check if I've signed up for Ovi with my phone number and send back the associated username) and the next time I logged onto the Ovi website, my preferred device had automatically been set to N8 (from the N82 that I had before). After setting up my account, it was easily able to sync with Ovi services - maps, contacts and email. I have never been bothered by Nokia for marketing purposes or anything else, and there's nothing on the phone that would 'phone home' to Nokia after the first time.

      --
      "..One hosts to look them up, one DNS to find them, and in the darkness BIND them."
    24. Re:maybe by cibyr · · Score: 2, Informative

      Did you get your N900 with PR1.2 already installed, did you install the PR1.2 update via SSU or did you install it via the firmware flasher?

      When I installed PR1.2 via SSU (how most users install updates; it's essentially a nice GUI on top of APT), after the reboot up popped a modal dialog asking me to accept the MyNokia T&Cs. The *only* way to dismiss this dialog is to accept the T&Cs, at which point it sends an SMS to Nokia. Sure, you can opt-out later, but by that point Nokia already has the data...

      --
      It's not exactly rocket surgery.
    25. Re:maybe by Anonymous Coward · · Score: 0

      Maybe. Somehow I got signed up to MyNokia even though I consider myself quite paranoid about these things. I repeatedly asked Nokia at which point I gave them my 'phone number and they repeatedly ignored the question while answering other questions. Either the 'phone can report it's number back to Nokia or Vodafone (my provider) do it and I didn't read the small print.

    26. Re:maybe by NuShrike · · Score: 1

      MeeGo will simply fail because of the arrogance of the Qt developers.

      Technical reasons:
      o one can NOT ask them on blogs, Jira, nor Twitter why Qt has such an uncompetitive and huge footprint in memory and storage for embedded, besides normal desktop
      o they don't care their software rendering path (new in 4.x and influenced by AGG) is also bloated in memory/storage and hurts them in the long-run for OGLES acceleration
      o they have 3-4 renderer paths inside Qt which all sit there taking RSS in the .so/dlls and is STILL without a clean, straight OGLES rendering path involving no such side conversions through an optimized specialized-purpose lib load (ie, instead of libGUI with EVERYTHING, libGUI_GL)
      o pointing out footprint issues AFTER using their qconfig and lots of work to already optimize/slash footprint, but devs will say you're an idiot and use qconfig. ... Exactly, wth.
      o one can NOT file a bugs in their Jira that Qt Creator takes 2x more memory than the MSVC equivalent (for even Qt code itself) without getting it shut down as invalid
      o if you submitted patches to switch their naive optimizations to tune toward more footprint-savings (because -O2 creates uselessly-bloated libs that aren't any benchmarked faster on mobile) they will "take it under consideration" and then ignore it
      o if you submitted patches into their Jira and are not a primary partner like Nvidia, they will nitpick the patch over tabbing and spacing (because it also fixes previous violations of their Style standards), ignore it the patch, and let it die on the vine

      Qt is simply not tuned for mobiles. Their internal forking of it as "Mobility" subversions helps themselves even less.

    27. Re:maybe by Anonymous Coward · · Score: 0

      Your "can't be done" is a bit of an exageration. You have always been able to take a photo using gstreamer from a terminal without a shutter release sound.
      The blob nature of any camera algorithmics should be irrelevant, as the loading of the driver and any firmware is done once at boot time, IIRC. You just need to mimic what the normal GUI does. You should be able to just use strace to see how the GUI does what it does. (You might need to tweak strace in order to delve into IOCTLs, but it's an open architecture - you can build your own strace.)

      But I share your pain. I think I was one of the first people to file a bug against the shutter sound limitation, and have it closed as a 'feature', way, way, way back.

    28. Re:maybe by Anonymous Coward · · Score: 0

      You have never developed software for a mobile device have you?

      As long as you want standards for development, android is the best platform ever.

    29. Re:maybe by Anonymous Coward · · Score: 0

      Nokia needs symbian.

      Symbian gives them an advantage over all other mobile OS platforms -- they can run the radio and apps off the same CPU. This isn't important at the very high end of the market, but nokia lost that market to Apple already. Symbian phones have the potential to be smaller, cheaper, and have longer battery life than any other mobile OS. Again, that doesn't matter to people who already need the Apple love, but for the other 80% of the mobile market, it's important.

      Nokia needs to start making CDMA phones. WTF are you guys doing walking away from the North American market? Make nice with qualcomm and get into bed with the carriers. Trouble is, it's likely too late for that already. Nobody wants to get into bed with a corpse.

      Link ovi with yahoo. Heck, *buy* yahoo. Sell symbian "feature" phones to people through verizon and link into their yahoo account. Again, you're not going to get the hipsters, but you know what, you already lost them.

      Make a land-line phone that runs symbian. Make it connect to the POTS network and to a sip provider.

      Open *all* of symbian. Let chinese companies who are right now using android use symbian instead, if they want. You need devices out there in the wild.

      Finally, fix the UI on symbian -- but for the love of god, keep supporting and developing T9 phones as well as the fancy touch-screen phones. Some people just don't want all the liabilities that come with a touch screen, and don't particularly want a qwerty keyboard on their phone. I love my e51, and don't plan on upgrading.

      Oh, and support blackberry connect everywhere. Make it a paid for app if that's what it takes, but at least make it an option. Again, it'd set you apart from the android horde.

      Oh, and I know none of this is going to happen.

      Sadly, Nokia is a rotting corpse with great bones.

    30. Re:maybe by hazydave · · Score: 1

      While that's a possible position, it's also the fact that Nokia's hurting on cash and losing market share. SymbianOS lost 10% share in the last year, and that's before people saw it going away. One big problem Nokia had was the simple fact that most SymbianOS users think they have a feature phone: they use the built-in stuff to browse the web, but they don't download apps. Most phones don't even come with the Ovi store app, and none did before mid-2009. So Nokia has pretty much guaranteed the grass is greener on the other side.

      In theory, Nokia should be doing well. They had a 50% share of the smart phone market in 2009, at least technically, and the smart phone market is the strongest and most profitable segment of the cell phone market. And yet, here's Apple, with less than 10% the market, making 30+% of all profit in the market -- more than Nokia, LG, and a few others combined. And the SymbianOS market is now down to 40%, and the year's not even over yet. That 40% sounds good, but not with -10% annual momentum behind it.

      Part of the problem, too, is that Nokia's offerings have matched their market position. Most of their "hot new" phones for 2010 look like someone else's idea of a hot new phone for 2008. And the better ones... are not on SymbianOS.

      If Nokia actually has the software chops to compete with their own OS, imagine if they tapped Android for the foundation, and built whatever they needed to distinguish themselves in the market on top of that. As it standard, they're doing some of that anyway with MeeGo, but without the traction that Android has. Maybe they have a clear plan with MeeGo, but they've also been doing Linux phones and devices a long time, and haven't really go anywhere with them. Why would MeeGo be different?

      It's not just an idle question, either. Smart phone sales in 2010 are about 250 million... Nokia has about 100 million of that action. By 2014, they're estimating that will double to 500 million. At their current rate of collapse, Nokia will be lucky to still be selling smartphones in 2014... they could realistically have only 10% of the market. And all those 500 million are not new customers... they're the same old customers, buying smartphones instead of feature or dumb phones. So Nokia's losing a big chunk of their non-smart market, and if they don't have a viable smartphone platform, those sales are going elsewhere.

      --
      -Dave Haynie
    31. Re:maybe by DragonWriter · · Score: 1

      Whose standards will those products follow once there is only one mobile OS that matters?

      Easy! Google's of course.

      Except (assuming Android wins), Google doesn't own Android.

      One of the first things Google did when it purchased Android was to create the Open Handset Alliance (OHA) and transfer Android to the OHA. (Which is one of the driving factors behind Android; many of the carriers, handset vendors, etc., pushing Android are part of the organization that owns Android.)

    32. Re:maybe by CarpetShark · · Score: 1

      I work for NOKIA and Google is our primary competitor

      NO. NOKIA is your primary competitor, until you sort out the problems that caused you to sabotage the N900's OS and create a whole bunch of ex-customers.

    33. Re:maybe by CarpetShark · · Score: 1

      "It's like comparing Windows to Linux">

      Perhaps, if Linux is version 0.01, and has been abandoned already.

    34. Re:maybe by Anonymous Coward · · Score: 0

      In what way is the N900 a hobbled PDA platform? I have a N900, but have never used the N800 or 770, so I have no basis for comparison, but as far as I'm concerned Maemo 5 on the N900 is a pocket computer with a phone added on, and it seems very open and not hobbled. As it is I don't think it makes a great smartphone platform and wouldn't recommend it to someone who isn't a geek that wnts to tinker with it to make it work just as they want, but it is very close to being great platform for the genreal consumer if only Nokia worked on fixing all the little issues with it.

      Throwing away Maemo 5 for Meego seems like a mistake to me considering how good Maemo 5 is to use, but Nokia's first Meego release is supposed to be based on what was to be Maemo 6 and not the same as the Meego development releases, so I'll have to reserve judgement on whether it was really a mistake or not until their first Meego phone is released.

  2. Why not by Anonymous Coward · · Score: 4, Insightful

    Maybe they don't like Android.
    That's why, in the face of Windows dominating the desktop, I installed Linux.

    It's possible for people to dislike software.

    1. Re:Why not by Anonymous Coward · · Score: 0

      That's only because Microsoft produces software that dislikes people.

    2. Re:Why not by gilesjuk · · Score: 1

      I think it's a case of Symbian being their code or feeling as if they have at least contributed a lot of it.

      Jobs said they considered Linux for the iPhone but ultimately didn't want to use someone else's code.

      Ballmer wouldn't use anything non-Windows.

      Nokia want to use their own software.

    3. Re:Why not by Deviate_X · · Score: 0

      Interesting that the Symbian was created to stop microsoft extending their desktop domination over phone manufacturers. After 10 years (of symbian) later its hard to see them using operating systems like Windows Phone 7, or Android which come with much more stringent specifications and hardware dictats.

    4. Re:Why not by Compaqt · · Score: 1

      Well, but Meego is actually Linux (combination of Moblin and Maemo).

      The reason for Symbian staying on is that it's great for low-battery usage. If someone buys a smartphone, they can expect to do a lot of charging. The least you can give lower/medium end users is long battery life.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
  3. I think Nokia understand phones by now by dbIII · · Score: 5, Insightful

    ... and also it is not costing them very much to develop the MeeGo environment.
    If they take up MS Windows Phone 7 that will be putting a vast amount of undeserved trust in what is really a competitor and hoping they will not get hurt. With respect to Ted Samson I think he is either not being serious and expecting to generate a spirited argument or he knows far less about what he is writing about than the youngest commenter here.

    1. Re:I think Nokia understand phones by now by martyw · · Score: 1

      Oh, really? They are making so many mistakes of late, for example in their lastest smartphone the N8 they omitted the "AppStore" - the OviStore from being included in the phone by default. What a move! I mean somebody in Cupertino must have had a long laugh and then a very good sleep knowing how badly managed their competitor's platform is.

    2. Re:I think Nokia understand phones by now by phishtahko · · Score: 5, Funny

      I bought an iPhone: brilliant engineering, highly intuitive.

      You mean like brilliantly putting the antenna on the outside of the phone so you could intuitively kill your signal by touching the phone?

    3. Re:I think Nokia understand phones by now by gilesjuk · · Score: 1

      MeeGo is the merger of Maemo and Moblin, so there's lots of man hours already been put into the platform. Personally I don't like the tab based approach to the UI. The icons are unclear and the tab selectors are small, not much use for people with fat fingers who are running it on a smartphone.

      The problem is current Nokia handsets with Symbian are probably just stop-gap until this project gets somewhere. I wouldn't want to put my money into buying an applications from the Ovi store if I knew that the phone's OS could be dead by the time the next handset came out.

    4. Re:I think Nokia understand phones by now by lyml · · Score: 3, Informative
      Jesus Christ not this again.

      Yes all phones lose signal strength when you cover the antenna, not all phones allow the antenna to be bridged with another antenna rendering it into a pretty crappy antenna.

      That's what the whole iphone antenna issue was about. Not signal attenuation do through holding it.

    5. Re:I think Nokia understand phones by now by Anonymous Coward · · Score: 0

      All cell phones suffer from that. Apple's new iPhone suffers from THE ADDITIONAL problem of detuning the antenna when you touch it in the natural places to touch it while holding it.

      An attenuated and detuned phone is worse than one that is just attenuated.

    6. Re:I think Nokia understand phones by now by Anonymous Coward · · Score: 0

      you must not be married. that most definitely is a feature.

    7. Re:I think Nokia understand phones by now by Anonymous Coward · · Score: 0

      ... and also it is not costing them very much to develop the MeeGo environment..

      I would really like to see this statement backed up with some data.

    8. Re:I think Nokia understand phones by now by stephanruby · · Score: 2, Insightful

      And also, MeeGo is not meant for the phone market, only Android is. MeeGo is meant for the mobile/wifi netbook/tablet market. In that sense, MeeGo is competing with ChromeOS, Windows 7, and Linux, and it will do very well in that regards with Intel backing it, Intel already dominates the Netbook market (just not on the OS side yet).

    9. Re:I think Nokia understand phones by now by Microlith · · Score: 1

      Are you the same guy who made this mistake over on ArsTechnica?

      MeeGo is definitely targeted for the phone market. Go actually look at documents that have been published and discussions on the mailing list. If it wasn't aimed at Android as well they wouldn't have an entire reference user interface for handsets.

    10. Re:I think Nokia understand phones by now by stephanruby · · Score: 1

      No, I've never posted on ArsTechnica, but I did attend the last day of the Intel AppUp Elements Developer 2010 conference in San Francisco. And if they do have a reference guide for handsets, which I am surprised that they do, it was certainly not their main focus during that conference.

    11. Re:I think Nokia understand phones by now by CarpetShark · · Score: 1

      You think Nokia understand phones? Really? Have you SEEN the amount of customers they have, bitching on their blogs about how they feel let down, etc.? It seems Nokia have even abandoned some blogs because of it.

    12. Re:I think Nokia understand phones by now by eugene2k · · Score: 1

      If you were attending Nokia's developer conference you would probably not hear much about developing apps for netbooks either.

      --
      Apple has "Mac vs PC", Microsoft has "Laptop Hunters", Linux has recession
    13. Re:I think Nokia understand phones by now by rtfa-troll · · Score: 1

      I wouldn't want to put my money into buying an applications from the Ovi store if I knew that the phone's OS could be dead by the time the next handset came out.

      A problem Nokia could make go away with one statement; "we invested 0.1% of our savings into buying VMware to write an emulator for symbian to run on Meego". Okay, I'm a little exaggerating on the price of VMWare, but seriously, how much effort would it take to guarantee backwards compatibility with most basic Symbian apps? Even better; it can be done as an application so it can be done by a completely independent separate group so there should be no effect at all on their OS delivery schedule.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    14. Re:I think Nokia understand phones by now by Rexdude · · Score: 1

      The way I understand it, the antenna is part of the metal back cover, which is what causes the attenuation on holding it.

      --
      "..One hosts to look them up, one DNS to find them, and in the darkness BIND them."
    15. Re:I think Nokia understand phones by now by Anonymous Coward · · Score: 0

      This comment for me solidifies my belief that Apple fans are so blind to their own platform's problems that they'll hand wave anything away.

    16. Re:I think Nokia understand phones by now by jwdb · · Score: 1

      That's only part of it. The iPhone apparently has two different antennas separated by an air gap. If you bridge that gap with your finger, you turn it into one large antenna that's badly matched to either of the original two tasks. This causes additional attenuation, beyond that caused by your hand.

      This also ignores the fact that by bridging the antennas, you're connecting the outputs of two power amplifiers. That makes me cringe somewhat.

    17. Re:I think Nokia understand phones by now by Anonymous Coward · · Score: 0

      The people running AppUp are not the ones you should listen to if you want to know where MeeGo is going... I'm quite sure those people have not yet understood what Moblin was and figuring out this MeeGo thing will take even longer: Notice how the appup site still offers a Moblin client download but nothing for MeeGo even though the 1.0 release was a some time ago. Notice how the appup client is not available in the moblin repositories (it's a proprietary shell script with a binary encoded in it). Notice how the client does not leverage the Moblin repos in any way and how it does not fit with the UX at all.

      These people are just looking at Apple and think "we want to copy that" without thinking of the difference of the platforms. They don't seem to understand that the system should avoid the weaknesses and and leverage the strengths of the platform not blindly copy something that will never work in the real world...

      The basic problem, I believe, is the same as within Nokia: People who control hardware products get to decide the direction, whereas the successful mobile platforms have a _software platform roadmap_ that trumps any single product roadmap.

    18. Re:I think Nokia understand phones by now by koiransuklaa · · Score: 1

      Nokia manufactures and sells phones for every phone market and protocol and have delivered at least a third of the worlds mobile phones for years and years. These days they sell about 500 million phones a year. Their logistics, manufacturing and sub contracting is phenomenally successful compared to the competition and often operates on totally different scales.

      There have been lots of news lately about Nokias problems but the tech blogs often forget to mention that financially they're not doing that bad -- In a technology manufacturing business any financial changes are just always radical so it's easy to make headlines like "Y/Y profit down 90%!". Many of these journalists forget to mention that the Nokia devices division profit is still calculated in billions: EUR 3-6 billion every year these past few years. 2010 will fit in that bracket as well.

      So... In light of the above I'd like to ask you this: If Nokia in your opinion does not understand mobile phones, who does? I hope to see something more substantive than number of blog comments to back the argument up.

  4. Also rans by freeshoes · · Score: 1

    Going with android immediately gives them relevance, and a great os. This is crunch time for them, if they make the wrong decision they will become also-rans against ios and android,

    1. Re:Also rans by rtb61 · · Score: 0

      They could also do what Google did and create their own Linux based operating system and maintaining compatibility in applications. Far more sensible than to get squeezed out in the Apple, M$ and Android battle. The catch with Android the battle of cost versus performance will be pretty fierce between manufacturers, as there is no real identity difference to ramp up margins with B$ advertising (the same for M$ offerings just that the prices are already loaded plus manufacturers lose control) as for Apple.

      The next big push will be interconnectivity smart phone connects to the smart book connects to the smart TV and Nokia is a limited electronics manufacturer and lacks the ability to produce a complete package deal.

      --
      Chaos - everything, everywhere, everywhen
    2. Re:Also rans by TheRaven64 · · Score: 4, Informative

      They could also do what Google did and create their own Linux based operating system and maintaining compatibility in applications

      That's what MeeGo is. Unlike Android, it uses a fairly standard stack (e.g. includes X11), so porting apps from the desktop is trivial - recompile, tweak the UI a bit for the small screen, ship.

      --
      I am TheRaven on Soylent News
    3. Re:Also rans by Anonymous Coward · · Score: 2, Funny

      Tweak the UI a bit?
      Understatement of the thread.

    4. Re:Also rans by Nursie · · Score: 5, Insightful

      Eh?

      The N900 does actually connect to the tv. Sure, with wires, but still. It also connects just fine to Mac, Windows and Linux machines I have, allowing them all net access and/or file transfer. It also picks up DLNA servers in the house and can use them as media sources.

      Nokia do a lot of things right. They've lost direction a bit over the last few years and the number of models they have now is just ridiculous, but if someone tightens the reigns and sorts out the business side, they've proven time and again how capable they are of producing solid, working devices with great user experience.

    5. Re:Also rans by TheRaven64 · · Score: 2, Insightful

      Depends on the target device. Current Maemo / MeeGo devices ship with a screen that does 800x480. It's 225dpi, so you do need to make some things bigger, but most apps that worked on smallish-screened desktops or laptops will be more or less usable on something like the N900. To make it really usable, you need some tweaking, but not a huge amount. If you want to scale it down to a smaller phone, then you probably need to completely redo the UI.

      --
      I am TheRaven on Soylent News
    6. Re:Also rans by neumayr · · Score: 1

      As a N900 owner, I disagree.
      If an UI looks like something I might expect on a desktop, if I'm forced to take out the stylus to use it, I look for alternatives and reevaluate my need for that app.
      At the very least, I would not pay for something like that, or recommend it to anyone. Which would be the only things Nokia would have an interest in.

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    7. Re:Also rans by neumayr · · Score: 1

      The next big push will be interconnectivity smart phone connects to the smart book connects to the smart TV[...]

      does not mean connecting you TV via a one-way TV-out.

      But the GP was very much mistaken with the rest of the sentence,

      Nokia is a limited electronics manufacturer and lacks the ability to produce a complete package deal

      Nokia being a very large corporation very large product portfolio. They could very well produce a smartphone - TV package, if they thought it made sense.

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    8. Re:Also rans by a_n_d_e_r_s · · Score: 1

      Good designed X11 program works in basically any screen size. Only bad programs hard code the graphical layout towards a specific screen size.

      --
      Just saying it like it are.
    9. Re:Also rans by Anonymous Coward · · Score: 0

      N900 is 266 dpi.

    10. Re:Also rans by risinganger · · Score: 1

      That really doesn't bode well for your average linux program then. I've had to learn a few new tricks just to use a standard 10" netbook and I'm talking about configuration screens - not even some esoteric application.

    11. Re:Also rans by Anonymous Coward · · Score: 0

      Sorry, not really. Have you ported anything to Maemo? Well, I have. GP was generally correct: Tweak the UI a bit, maybe fix a few things in debian/rules. Ship.

    12. Re:Also rans by kitgerrits · · Score: 1

      I'm still waiting for a decent DLNA client for my Android phone...

      --
      "I was in love with a beautiful blonde once, dear. She drove me to drink. It's the one thing I am indebted to her for."
    13. Re:Also rans by Anonymous Coward · · Score: 0

      The next big push will be interconnectivity smart phone connects to the smart book connects to the smart TV and Nokia is a limited electronics manufacturer and lacks the ability to produce a complete package deal.

      Have you never seen an n900? They are the closest to your "complete package deal".

      Hooks up to a tv via digital cables, granted... they aren't hi def. But they're digital and everything looks pretty nice.

      Currently has usb host mode hack in the works. Meaning you can hook a usb keyboard and/or mouse to it.

      Can print on a network via CUPS.

      Has openoffice and pdf support so you can work on pretty much any document you might need to.

      I bet everyone was excited this month when they finally released a beta of firefox for android. N900 has had firefox betas for a year now.

      And I see the other guy has mentioned the other neat entertainment stuff like detecting DLNA on a network, etc. It was also the first handset to have fully functioning flash. Oh, and that whole integrated Skype thing. And all those Jabber protocols.

      And this is all using maemo, which Nokia is pretty much ditching for meego.This is what has been accomplished in a year using something that no one should care about. Meego handsets will likely have all this going for them at the very beginning or shortly thereafter release.

        I bought a touchscreen laptop around the time the n900 was released. The price for the laptop was about 900 dollars, and the n900 was probably pretty close to the same price. One year on, my laptop is an overheating pile of shit and I hate it. But I don't really care because I use my n900 for pretty much everything internet related anyway. Hindsight being what it is, i would have gotten a cheaper laptop and sprung for the n900 as soon as it was released.

      I don't use my phone like people use their iphones. I use my phone like most people use their laptops.

      What were you saying you wanted again?

    14. Re:Also rans by Anonymous Coward · · Score: 1, Insightful

      The next big push will be interconnectivity smart phone connects to the smart book connects to the smart TV[...]

      does not mean connecting you TV via a one-way TV-out.

      What? I'm sort of lost on what data you would want to share with your monitor other than visual data. The device can get or share data via usb or wifi.

      The only data I can think of is that you might want your phone to receive data from a touchscreen monitor? If so...*shrugs*

      If you're saying you want a star trek device that everything hooks up to and you just plop it in a cradle and BAM SUPERCOMPUTER...this is not it. Nothing currently available is. But it meets most of the basic outlines these people are asking for.

      Every nokia meego discussion on slashdot/reddit/digg brings this mythical device up. And n900 users say "not it, but close!" And everyone largely laughs at them, quietly shifts the goalposts and says "Nooo, what I want has to include all this, have 1 week battery life, run crysis, fit in my pocket, drive my car to work for me, give me the ability to see ghosts, have a camera that can take photos of molecules/distant galaxies, have an apple logo on it, and...".

      Somewhere in that laundry list of needs you discover you're probably talking to someone that is nine to thirteen years old.

    15. Re:Also rans by Spugglefink · · Score: 1

      Tweak the UI a bit? Understatement of the thread.

      I agree this is a huge understatement, and that the people who commented further down about how easy this is have never worked on trying to port an application of any size or consequence to this device.

      The hardest thing is that while the screen real estate you've got to work with seems ample, a well-designed app has to have touchable control surfaces, and this requires the use of on-screen controls that are absolutely enormous relative to the number of pixels available. This really limits the number of controls you can fit on a screen.

      Make them too small, pack them too close together, and the interface doesn't work well. It's even possible to get false readings with the stylus, because the responsiveness of this touch screen really is pretty seriously crappy. I've plotted data points from attempting to touch the same control 100 times in a row; it's a shotgun blast doing it with a finger, and the stylus brings that down to something more like a short-barreled pistol shooting really big, ragged groups. An accurate input device, this screen ain't.

      It may be trivial to port some text editor or something of the sort, but try implementing something like the GIMP on this thing. For instance, just my standard tool palette in the GIMP measures about 170x212 as sampled from my desktop screen. It uses 32x32 icons, which are quite small for use on the N900. A more comfortable version of this tool palette would use 64x64 icons, and now you've got 340x424 out of 800x480 devoted just to one small tool palette, which is just a small portion of a much larger standard control palette in the GIMP.

      It would be possible to get the GIMP to run on this thing (I suppose; I'm actually a Qt guy, and I'm treating the GIMP as though it were a Qt application for this thought exercise), but it would require considerable thought and planning to execute all of that interface on this scale and still leave the user some room to actually do something interesting with the tools.

      In short, we're not talking a little tweak, we're basically talking about a fork, possibly within the same code tree as the original UI. It's going to have to have some dramatic amount of work done to cut it up and think about how to present what for maximum utility. This would a be a huge project, and the majority of software I use on my desktop fits into this same kind of category. Try porting Rosegarden to this thing, for instance, ignoring the fact that conventional Linux audio is basically impossible to do on the N900 in the first place. Rosegarden barely functions on a 1024x768 desktop display, and scaling it down to 800x480 would require a massive and complete rewrite of the entire GUI from the ground up.

      I just can't see how anybody who has ever worked on any sort of complicated graphical application could think porting to this device is as simple as unpacking a tarball, firing up the cross-compiler, and then doing some minor tweaking. Not unless completely rewriting just about every part of the entire user interface to work in this form factor is "minor" anyway.

    16. Re:Also rans by Anonymous Coward · · Score: 0

      Agreed..N900 very diverse and powerful features, like having a nearly full on linux box in your shirt pocket. Why not Maemo? WTF wrong with Maemo?

      IMHO, better than Symbian, ..the best I hope for in MeeGo is that it's "as good as" Maemo someday.. why not hitch the Nokia Wagon to Maemo?

      I have very little confidence that Nokia can even get out of their own way..and fearful that my next device will be only "almost as good" as my N900

  5. About bloody time! by Toy+G · · Score: 1

    Ouch. I didn't think Nokia would ever muster the balls to kill off Symbian (which was clearly the only logical move after the iPhone ate its lunch, even more so after Android started making inroads). I guess the majority of those 1800 redundancies will be Symbian geeks, to be replaced by Linux ninjas working on MeeGo (here's hope).

    It's a shame it took so long for them to understand. They should have ditched Symbian right after the N97 disaster, pushing hard on shipping great Maemo products. Instead, Maemo was the unloved stepchild and was basically ditched for Moblin, losing another year of development... They are at least two years behind Android and need to catch up fast, to have a chance to stay relevant in the next decade. That MeeGo phone has to come out in Q12011 and blow Android out of the waters. Anything less than that, and they're toast.

    --
    -- Let's go Viridian.
    1. Re:About bloody time! by TheRaven64 · · Score: 4, Informative

      Ouch. I didn't think Nokia would ever muster the balls to kill off Symbian (which was clearly the only logical move after the iPhone ate its lunch, even more so after Android started making inroads).

      What? Symbian has a beautifully designed kernel, with power management at every level of the stack, able to run isolated personalities so that it can run the hard-realtime stuff for controlling the radio on the same CPU as the apps. It has a microkernel design with support for capabilities (for running semi-trusted code), and concurrency at every layer from the nanokernel up so it will scale happily on the next generation of phones with multiple cores.

      Linux, in contrast, is a pig on mobile devices. Power management is accomplished by hacks on top of hacks. Hard realtime is a joke. It's there purely for buzzword compliance.

      Unfortunately, the userland stuff for Symbian is a pain. It used to use a version of C++ for userspace development that exposed some of the very low-level memory management stuff. This was important for phones with no MMU, but is a waste of time now. It's not required (in fact, you can just use Qt), but a lot of people tend to judge Symbian by either that or by the crappy UIs that a lot of manufacturers (including Nokia) have built on top of it in the past.

      --
      I am TheRaven on Soylent News
    2. Re:About bloody time! by RichiH · · Score: 1

      The irony is that with Qt, the userland started to look good for Symbian.

      Though the _real_ problem is the fragmentation. And I am not talking Steve Jobs make-believe fragmentation. When I still used to follow Nokia & the Ovi blogs closely, they would announce Application X which is available for Symbian 5 devices, second release, fourth generation, with touchscreen and the optional chicken attachment. The E75 still does not have free navigation even though it supports Ovi Maps in its newest iteration. Etc, etc.

      Long story short? My E75 (which can do email, web, you name it) has a broken SIM card and is used as my alarm. The HTC Desire is used more than my laptop for pretty much everything. And I am hoping to migrate to Meego in the long run as more open is better. Always.

      PS: I know that Meego needed to move fast (har har), but going with RPM over DEB was a dire mistake.

    3. Re:About bloody time! by myzz · · Score: 1

      If the kernel is so good, couldn't they write some linux-like syscall compatibility layer on top of it or emulate linux in libc?

    4. Re:About bloody time! by TheRaven64 · · Score: 1

      They do provide a POSIX compatibility layer (PIPS), so you can recompile POSIX code. The only big thing missing is fork(), which can't be implemented easily on the Symbian kernel. That's not a huge problem - fork() is horribly inefficient in a modern *NIX system anyway (it requires marking the entire address space as Copy on Write and doesn't interact nicely with threads).

      Adding a syscall layer would probably be possible, but not really interesting - it's not like there's a large collection of binary-only ARM Linux software.

      I'd love to see a Symbian kernel, with a UNIX-like userland and X11, but I don't think it's anywhere on the roadmap.

      --
      I am TheRaven on Soylent News
    5. Re:About bloody time! by neumayr · · Score: 1

      PS: I know that Meego needed to move fast (har har), but going with RPM over DEB was a dire mistake.

      Care to elaborate? I'm pretty much unfamiliar with RPM, but DEB performance is already annoying on my overpowered desktop and notebook, on my N900 it really sucks.

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    6. Re:About bloody time! by Anonymous Coward · · Score: 0

      That's nonsense, Linux has hard real-time and Linux phones that run on a single CPU (both datamodem and apps) have been available for years. Linux has several well proven real-time options, including a seperate real-time kernel and real-time extensions in the Linux kernel itself (such as RT-PREEMPT).

      Power management does remain a problem on Linux, though.

    7. Re:About bloody time! by maestroX · · Score: 3, Informative

      I'd love to see a Symbian kernel, with a UNIX-like userland and X11, but I don't think it's anywhere on the roadmap.

      It's on the map, in another region: QNX.
      Acquired by RIM recently, so expect the BlackBerries to run it in the future.
      (Unfortunately closed-source again after acquisition)

    8. Re:About bloody time! by ObsessiveMathsFreak · · Score: 1

      It's not required (in fact, you can just use Qt), but a lot of people tend to judge Symbian by either that or by the crappy UIs that a lot of manufacturers (including Nokia) have built on top of it in the past.

      That's because at the end of the day a phone is a consumer device, and the user interface is probably the most important part of the product--aside from the cost of course.

      --
      May the Maths Be with you!
    9. Re:About bloody time! by Anonymous Coward · · Score: 0

      You don't need hard real-time on smartphones. And since you brought it into discussion, have you ever tried Xenomai on a beagleboard (a trivial example, of course)? I guess not ...
      Guess what! On a BB, you can't get average latencies higher than 18 microseconds. I would call that hard-real time. Wouldn't you?

    10. Re:About bloody time! by RichiH · · Score: 2, Insightful

      1) You lose easy access to the largest repository on Earth (Debian's). And Debian has a dedicated ARMel distribution. This is _massive_

      2) When I still used RPM-based distros, I could make the package DB go boom by just installing/uninstalling stuff

      3) I know how to package DEBs. Not true for RPM.

      4) The decission was made behind closed doors.

      5) I use Debian for laptops, desktops, servers, I would prefer to use Debian-esque on my mobile.

    11. Re:About bloody time! by 21mhz · · Score: 1

      3) I know how to package DEBs. Not true for RPM.

      And this is somehow one of the reasons why Nokia is wrong?

      --
      My exception safety is -fno-exceptions.
    12. Re:About bloody time! by RichiH · · Score: 1

      No, but it's still something that is relevant to me.

    13. Re:About bloody time! by neumayr · · Score: 1

      1) Aside from CLI tools, there's nothing in those repos that would work on mobiles. And those are likely to be found in RPM repos too.
      2) I assume that's fixed in one of the oldest linux package manager.
      3) ...
      4) Politics. Yeah well, there are more unfortunate political decisions to be annoyed by.
      5) ...

      Not very convincing. If those things buy me package management with acceptable performance, yay, RPM ftw!11!

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    14. Re:About bloody time! by RichiH · · Score: 1

      > 1) Aside from CLI tools, there's nothing in those repos that would work on mobiles. And those are likely to be found in RPM repos too.

      apt-get install hex-a-hop # you were saying?

      > 2) I assume that's fixed in one of the oldest linux package manager.

      I assume that's not the case. Yay, stand-still.

      > 4) Politics. Yeah well, there are more unfortunate political decisions to be annoyed by.

      Ah, true. That makes in better in this case.

      > Not very convincing. If those things buy me package management with acceptable performance, yay, RPM ftw!11!

      My limited experience with current CentOS & SuSE is that it's slower to update a load of packages than on Debian.

    15. Re:About bloody time! by neumayr · · Score: 1

      Hex-a-hop is on the Maemo repos. Would expect that to work on Maemo devices.
      That Nokia decides things about their new OS without consulting the public is a given, and the choice of a package manager is pretty fundamental. How would you have preferred them to handle it, realistically?

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    16. Re:About bloody time! by juhaz · · Score: 1

      1) You lose easy access to the largest repository on Earth (Debian's). And Debian has a dedicated ARMel distribution. This is _massive_

      There's a kernel of truth in this one, but it's unlikely they would be directly usable because of library version differences, and even if they were, vast majority of the applications there are horribly suited for mobile devices.

      2) When I still used RPM-based distros, I could make the package DB go boom by just installing/uninstalling stuff

      You've got to be kidding. Because of the ridiculous "half-installed" state, Debian package DB goes boom everytime something goes even a slightest bit wrong during installation. Been using Ubuntu, Debian and Fedora side by side for a long time, last time I've seen a broken RPM database was maybe in RH8 or FC1. Deb systems? Still all the time.

      3) I know how to package DEBs. Not true for RPM.

      I know how to package RPM's. They're pretty damn simple, DEBs on the other hand require some arcane magic.

      4) The decission was made behind closed doors.

      Yes, pretty much just like every other company's every decision.

      5) I use Debian for laptops, desktops, servers, I would prefer to use Debian-esque on my mobile.

      You should really hope very hard this isn't one of their considerations, if it were, Windows Mobile would be the only logical choice.

    17. Re:About bloody time! by RichiH · · Score: 1

      > You've got to be kidding. Because of the ridiculous "half-installed" state, Debian package DB goes boom everytime something goes even a slightest bit wrong during installation. Been using Ubuntu, Debian and Fedora side by side for a long time, last time I've seen a broken RPM database was maybe in RH8 or FC1. Deb systems? Still all the time.

      apt-get install -f

      > I know how to package RPM's. They're pretty damn simple, DEBs on the other hand require some arcane magic.

      git-buildpackage

      > Yes, pretty much just like every other company's every decision.

      Cool, so how does that affect the fact that the community had a reasonable expectation (Qt...!) for things to be different.

      > You should really hope very hard this isn't one of their considerations, if it were, Windows Mobile would be the only logical choice.

      Not sure if troll..?

    18. Re:About bloody time! by juhaz · · Score: 1

      You've got to be kidding. Because of the ridiculous "half-installed" state, Debian package DB goes boom everytime something goes even a slightest bit wrong during installation. Been using Ubuntu, Debian and Fedora side by side for a long time, last time I've seen a broken RPM database was maybe in RH8 or FC1. Deb systems? Still all the time.

      apt-get install -f

      Yes, it's usually fixable. But it shouldn't break in the first place. And -f isn't always enough, it's still fixable by hand in those cases, but end-users can't do that.

      You should really hope very hard this isn't one of their considerations, if it were, Windows Mobile would be the only logical choice.

      Not sure if troll..?

      It's not a troll. It's perfectly valid extrapolation of your argument. You claim it should be Debian because you use Debian. Well, vast majority of their potential customers don't use Debian on their desktop, they use Windows. Therefore, if the mobile platform should be influenced by users' desktop of choice, it should be windows.

  6. Why ditch it? by vadim_t · · Score: 5, Insightful

    Making themselves yet another Android vendor would give little reason for people to prefer their phones over somebody else's.

    Also I find Nokia's approach interesting. Their distribution is a very standard looking one, and porting applications to it is extremely trivial. Anything that compiles on ARM will run outright, and only needs fixes to the UI. Lots of command line tools can be used without changes.

    1. Re:Why ditch it? by jklovanc · · Score: 1, Insightful

      Making themselves yet another Android vendor would give little reason for people to prefer their phones over somebody else's.

      Different is not necessarily better. As a consumer I can buy a Droid phone and in the future buy another driod phone from another compatible manufacturer and still use the same apps. If I buy a Nokia, I am stuck buying Nokias if I want to use the same app.
      There is also the catch 22 of any new OS; Few apps are written because the install base in not high enough, Install base is low because there are few apps. iOS avoided that issue because they were the first on the block and every developer wanted to get on their band waggon. Android avoided that issue because there are enough people that are dissatisfied with Apple's closed system that an open system has a place. It sounds like MeeGoo will be just another closed system like iOS; one manufacturer, one app store, my way or the highway. MeeGoo will be behind iOS and Android forever causing every app publisher to make the decision whether or not to support a third OS. The answer to that question for many developers is no.

      Also I find Nokia's approach interesting. Their distribution is a very standard looking one, and porting applications to it is extremely trivial. Anything that compiles on ARM will run outright, and only needs fixes to the UI. Lots of command line tools can be used without changes.

      My first question is; how many people will be running command line tools on their phone?
      Second the code must run on an ARM so must be written for an ARM. Can I easily port my Android or iOS app to MeeGoo? I doubt that very much. Which means that I need to write apps for a third OS. Not a good decision if i can cover 95% of the current market buy supporting iOS and Android.

    2. Re:Why ditch it? by justleavealonemmmkay · · Score: 1

      Making themselves yet another Android vendor would give little reason for people to prefer their phones over somebody else's

      I was (no longer since the crappy N97) a great Nokia fanboi. They simply make the best hardware, and have kept understanding that a smartphone should be a phone with PDA functions and not the other way around. The OS has nothing to to with it; its only advantage at one time was that is was the only game in town, especially at a time where the competition was windows mobile, which is a badly hacked version of a PDA OS that was not very good to begin with. Not so anymore with IOS and Android But as a would be programmer and generally as a geek, I simply hate Symbian. I would certainly buy a Nokia Android. Or the best of both world; it should not be tremendously hard to make the Dalvik VM run on Symbian.

    3. Re:Why ditch it? by vadim_t · · Score: 1

      What Symbian? What I have is a N900, there's no trace of Symbian in it as far as I can tell. What runs on the N900 is a very standard looking Debian based distribution.

    4. Re:Why ditch it? by Anonymous Coward · · Score: 0

      My first question is; how many people will be running command line tools on their phone?

      People who know how to write a script. I don't program for a living and I doubt anyone else would want to use what I write. I don't care if my phone is the only one in the world they run on. If I can get a linux distro on a phone that I can run any apps compiled for arm and use scripts started from a menu to do it, I'm happy.

      Captcha: amateurs (how did they know?)

    5. Re:Why ditch it? by xnpu · · Score: 1

      ARM = Maemo/N900.
      Meego is being developed on Intel nightmare chips. The ARM port of MeeGo is not supported.

    6. Re:Why ditch it? by vadim_t · · Score: 1

      Not supported on N900 certainly, but that makes sense. As far as I can tell, Nokia has no intention of switching away from Maemo on N900, Meego will be used for a future device.

      Or you mean Nokia is going to release an Intel based phone?

    7. Re:Why ditch it? by MrHanky · · Score: 3, Insightful

      My first question is; how many people will be running command line tools on their phone?

      Plenty of really excellent GUI apps (some of them made with Qt) are simply front-ends to complex command line utillities.

    8. Re:Why ditch it? by Anonymous Coward · · Score: 0
      (posting anon as I already moderated)

      As far as I can tell, Nokia has no intention of switching away from Maemo on N900, Meego will be used for a future device.

      This is partially true - while Meego won't be officially supported on the N900, the upcoming PR 1.3 update (which should be coming quite soon - exactly when is unknown) will allow dual-booting Meego as well. This is intended for developers and enthusiasts, I know I'll try out Meego once 1.3 is out.

    9. Re:Why ditch it? by neumayr · · Score: 2, Funny

      Captcha: amateurs (how did they know?)

      The stench of armchair software engineers =)

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    10. Re:Why ditch it? by neumayr · · Score: 1
      Yeah well, the N900 doesn't match the parent's requirement:

      ...a smartphone should be a phone with PDA functions and not the other way around.

      It's more like a too small tablet with not that great voice support and the redeeming feature of a keyboard.
      Don't get me wrong, I really like that thing. But that's because I use it like subnetbook most of the time.

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    11. Re:Why ditch it? by Anonymous Coward · · Score: 0

      Why? Sony Erricsson has done the same and they're pretty successful with it. In any case, more successful than they ever were with Symbian and they're making a profit.

      IMHO Android is simply a base requirement these days, on top of which vendors can build value.

    12. Re:Why ditch it? by grumling · · Score: 1

      I wonder if Maemo and Nokia would be in the same place they are now if they would have kept the same size and form factor of the N810 when they put out the N900?

      I've moved on to an Android device mostly because the screen and keyboard on the N900 was just too small to be useful for me (and the useless kickstand...). I still use my N810 as a photo viewer and Sykpe phone, while the N900 is in a closet. Maybe I'll get it out again when 1.3 is released, but I don't think I'll go back to using it on a daily basis, unless there's some very compelling reason (like Skype video calling).

      --
      "Well, good luck finding a judge that doesn't run a bestiality site."
    13. Re:Why ditch it? by Anonymous Coward · · Score: 0

      MeeGo has also MooGo compliance specification, application compatible with MeeGo should run in all MeeGo devices.
      Differentiation in devices does not mean nor even involve breaking this specs. Actually, if you break it, you can't any more
      call is as MeeGo.

    14. Re:Why ditch it? by vadim_t · · Score: 1

      Different is not necessarily better. As a consumer I can buy a Droid phone and in the future buy another driod phone from another compatible manufacturer and still use the same apps. If I buy a Nokia, I am stuck buying Nokias if I want to use the same app.
      There is also the catch 22 of any new OS; Few apps are written because the install base in not high enough, Install base is low because there are few apps. iOS avoided that issue because they were the first on the block and every developer wanted to get on their band waggon. Android avoided that issue because there are enough people that are dissatisfied with Apple's closed system that an open system has a place. It sounds like MeeGoo will be just another closed system like iOS; one manufacturer, one app store, my way or the highway. MeeGoo will be behind iOS and Android forever causing every app publisher to make the decision whether or not to support a third OS. The answer to that question for many developers is no.

      N900 is extremely open actually. You can entirely reformat and repartition it if you wish. You can install Android, Ubuntu or anything else you want on it.

      I don't know how will this work out long term, but IMO it has a big advantage is that very little porting required. There isn't as much need to get on the bandwagon because a lot of what can be used on Maemo/Meego is stuff that makes perfect sense on the PC.

      My first question is; how many people will be running command line tools on their phone?

      Lots. They just won't know it. The NFS tools are commandline tools for instance. If you want to set up a pretty GUI for NFS on the N900 you already have the tools to do the job. All you need is to write a little GUI to use them.

      Want your app to do some image processing? You can install and call imagemagick.

      Second the code must run on an ARM so must be written for an ARM. Can I easily port my Android or iOS app to MeeGoo? I doubt that very much. Which means that I need to write apps for a third OS. Not a good decision if i can cover 95% of the current market buy supporting iOS and Android.

      It must not be written for an ARM. It must compile on ARM, which the vast majority of Linux software does. Ubuntu has an ARM version.

      Can I easily port my Android or iOS app to MeeGoo?

      For Android, I'm pretty sure it will be possible to run the apps. I don't know much about how Android development works, but I don't see anything stopping the existence of a Dalvik package for Meego, and some sort of compatibility layer. You can use a chroot, VM, whatever approach is needed to get it to work. It's possible to install Android on the N900.

      iPhone probably not, but then I'm quite sure that Apple would really hate such a thing.

      I see the issue differently: To target Android or iPhone I've got to write for their specific SDK. To target the N900 a lot of the time I can reuse code that runs in any normal Linux distro, and just adjust the UI as needed.

    15. Re:Why ditch it? by gmuslera · · Score: 1

      It sounds like MeeGoo will be just another closed system like iOS; one manufacturer, one app store, my way or the highway. MeeGoo will be behind iOS and Android forever causing every app publisher to make the decision whether or not to support a third OS. The answer to that question for many developers is no.

      Uh? Not fully sure about Meego, but in the Maemo/N900 you DONT need to use Nokia's app store, there are several non official repositories already. And regarding one manufacturer... Meego won't go just to smartphones, you have at the very least Intel on board, is open (dare to touch a line of iOS, or to legally to download it to put in your own phones), and intended for not just phones, but car computers, tablets, netbooks and other devices. Even sticking in Nokia's world, using QT for development of apps for it, mean that your apps could come from/to linux/symbian/windows/etc if using that libraries. If you want to compare it with something, think in Android.

      My first question is; how many people will be running command line tools on their phone?

      Your graphical app could be the one running command line tools too.

      Second the code must run on an ARM so must be written for an ARM. Can I easily port my Android or iOS app to MeeGoo? I doubt that very much. Which means that I need to write apps for a third OS.

      The code must be COMPILED for ARM to run on ARM. In particular in Meego is intended to run in Intel (you know, is not coming just from Nokia) and ARM systems. What you can easily port is your Linux and/or QT app for it

    16. Re:Why ditch it? by neumayr · · Score: 1

      Video calling is implemented on 1.2. No idea how well it works though.

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    17. Re:Why ditch it? by metamatic · · Score: 1

      Making themselves yet another Android vendor would give little reason for people to prefer their phones over somebody else's.

      They could sell Android phones with a standard Android image and no lockdown, i.e. sell the Android equivalent of the N900. I'd go for that, and nobody else seems to be doing it.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    18. Re:Why ditch it? by Anonymous Coward · · Score: 0

      You can trivially port any Qt-based desktop app... That's huge! Also, Qt is a lot easier to work with than the freaking annoying Android Java API IMHO..

    19. Re:Why ditch it? by Anonymous Coward · · Score: 0

      Oh so next Nokia phones will run on Intel hardware? Dream on.

      I'm sure this is what Intel is hoping in the long run, but if you think it will happen now, you're delusional. Where MeeGo "is being developed" isn't that relevant: I'm sure Maemo developers mostly worked on Intel chips too.

      Intel doesn't want to support ARM themselves, that's not a surprise. They've also said they have nothing against MeeGo doing that as long someone else does the work.

    20. Re:Why ditch it? by Eunuchswear · · Score: 1

      It sounds like MeeGoo will be just another closed system like iOS.

      "MeeGo is an open source project created by merging the Moblin and Maemo software platforms, and is led by the MeeGo Technical Steering Group (TSG). The governance model is based on meritocracy and the best practices and values of the Open Source culture. The MeeGo project lives under the auspices of the Linux Foundation."

      http://meego.com/about/governance

      Not so closed. Not single manufacturer.

      --
      Watch this Heartland Institute video
    21. Re:Why ditch it? by jklovanc · · Score: 1

      OK I'm wrong. So it is just another Android. The point is that it is not different from the two big players on the market today.

    22. Re:Why ditch it? by Eunuchswear · · Score: 1

      No, it's not another android:

      MeeGo is a full linux, with a linux userland as well as kernel.

      Code runs native, not in an interpreted virtual machine.

      The kernel is the standard Linux kernel, without weird "extensions" for power management. (Google tokenised dead mice for details).

      Development is done in the open, not behind closed doors at Google with the great unwashed getting a look at what's going on when Google feel like it.

      Maybe the consumer thinks this "doesn't matter", but then the consumer thinks Microsoft write good software.

      --
      Watch this Heartland Institute video
  7. Lots of reasons by Microlith · · Score: 5, Insightful

    The first that comes to mind is how Android is all about tossing aside everything that is open source as we know it and reinventing the wheel. The catch is that the wheel has not necessarily been improved, and now it's all under the control of Google, who does development behind closed doors and only allows hardware vendors to participate in the process. The rest of the world gets Android code when Google feels like releasing it.

    The open source world has TONS of excellent APIs, no sense in not using them. Makes development a lot easier when you don't have to worry about each subsystem yourself. And hey, if your hardware vendor isn't run by bean-counting, control freak assholes, you can participate too.

    But the main reason Nokia won't go Android is because that makes them dependent on Google, which even Android vendors like Motorola cite as a risk. Google wants to ride other vendors to get their services out there and make money, and that's a realm Nokia wants for themselves.

    Following along with this, I'm amused that people put WP7 in league with Android or MeeGo. It's more like an iOS 2.0 you can license, and well you only need to read my post history as of late to know my opinion on hyper-restrictive OSes like iOS and WP7.

    1. Re:Lots of reasons by Anonymous Coward · · Score: 2, Interesting

      It seems that even hardware vendors don't have much influence on Google for Android development. Most of them don't get the build before the rest of the world does. So it means that if you're not HTC or one of the close partner, you'll always be lagging. And even the close ones have little input into the development process.

      Nokia does not want the phone market to become like the PC market, where you have one Microsoft and lots of OEMS.

      Meego is an Open Source project done right, with open development, re-use of existing components, etc. We should support it fully.

      I expect that in some time, other major OEMs will join too and not just in the mobile phone vertical, but in other verticals too (like Bosch in the in-car vertical).

    2. Re:Lots of reasons by perbu · · Score: 1

      The rest of the world gets Android code when Google feels like releasing it.

      The open source world has TONS of excellent APIs, no sense in not using them.

      What sort of APIs are your talking about? Much of what existed pre Android was software built primarily for desktop use, disregarding things like battery and memory usage and implementing a feature set far greater then what is needed on a phone - like the X window system. Nokia tried porting a true GNU system to a phone with Maemo, but it looks like it wasn't much of a success.

    3. Re:Lots of reasons by Anonymous Coward · · Score: 1, Interesting

      Car vertical seems to be happening already - GENIVI chose Meego; when looking only at car manufacturers among its members, you have there already BMW, GM, Peugeot Citroen, Hyundai, Mitsubishi, Renault Nissan Samsung, Tata; not bad at all.

    4. Re:Lots of reasons by RichiH · · Score: 1

      ()()
      ('')
      (__)

      My bunny is clearly superior to yours. Also, it acts as a Kirby if need be.

    5. Re:Lots of reasons by Anonymous Coward · · Score: 0

      To all the 11 year olds who downloaded $2000 of 'apps' in their first billing cycle.

      Apple has an app storefront, Google has, and Nokia would like one too to get 'locked in' customers.
      MS also has designs, and so do the card merchants (Visa+Mastercard). Oh and blooberry - me too, and HTC has designs...

      In the soap powder or cola wars, economics 101 tells us there will be only 2 winners, and one is already Apple who will be very hard to knock off their perch.

      Users don't care where they get it, but sure as daylight the 'vendor' wants to lock hardware so it can cream off a 20% plus of everything portal fee.

      Google's SKYPE attraction on mobiles is unbeatable, and the rest of World (ROW) and low income China, India and Asia - that is HUGE pull power, and MS can't beat or compete with Android in raw numbers - and maybe power efficiency = battery life.

      Its a safe bet Nokia is doomed, unless Google does something vile and stupid, like disallow money transactions bypassing its roadblocks - unless MS decides to buy them out because MS is no longer agile enough to keep up with monthly hardware releases.

    6. Re:Lots of reasons by Microlith · · Score: 1

      Nokia tried porting a true GNU system to a phone with Maemo, but it looks like it wasn't much of a success.

      Which was not a function of the OS, but of user experience handling and marketing. It's not the substructure that sells a phone, it's the user interaction and integration.

      The point is that there's no need for a wholly custom set of APIs for mobile devices.

    7. Re:Lots of reasons by Anonymous Coward · · Score: 0

      The first that comes to mind is how Android is all about tossing aside everything that is open source as we know it and reinventing the wheel. The catch is that the wheel has not necessarily been improved, and now it's all under the control of Google, who does development behind closed doors and only allows hardware vendors to participate in the process..

      Considering that the whole Android stack is open sourced, I wouldn't call it "behind closed doors".

    8. Re:Lots of reasons by Anonymous Coward · · Score: 0

      "It seems that even hardware vendors don't have much influence on Google for Android development. Most of them don't get the build before the rest of the world does. So it means that if you're not HTC or one of the close partner, you'll always be lagging. And even the close ones have little input into the development process."

      I would mod you up if I could. This is the honest and scary truth. Google chooses who gets the latest code. Code is only open sourced after release. The public has no influence on new features or design. It is Google's platform, and they let the manufacturers know it by stabbing them in the back when they feel like it. How long was it between the release of the Motorola Droid and the open source release of Eclair? And what happened with Froyo?

      Posting AC since I work in handset development for one of those manufacturers Google likes to screw with.

    9. Re:Lots of reasons by DragonWriter · · Score: 1

      The first that comes to mind is how Android is all about tossing aside everything that is open source as we know it and reinventing the wheel. The catch is that the wheel has not necessarily been improved, and now it's all under the control of Google, who does development behind closed doors and only allows hardware vendors to participate in the process.

      FIrst, Google doesn't own Android, the Open Handset Alliance does (Google did briefly, when it bought Android and before the OHA was put together.)

      Second, Android development is done through the Android Open Source Project. Nothing excludes participants (including individuals) who are not "hardware vendors" from participating.

      Which is unsurprising, given that most of the Open Handset Alliance members themselves aren't hardware vendors, including the software and online services companies that no doubt have just as much interest in the actual Android platform software as the hardware companies.

  8. Nokia isn't exploiting the right opportunities. =\ by Anonymous Coward · · Score: 0

    If Nokia was smart, they would see the opportunity in developing MeeGo for what it excels at. Which in my opinion, is a netbook OS. They have plenty of opportunity there, with a netbooks low price and burgeoning popularity in US, European, and Asian markets they could very easily start building a new empire. Emerging consumer nations such as China and India will be having more and more people buying their first time computer and this could be a great foot in the door for building interoperability with future phone products. I also think Android is a great platform and Nokia should drop Symbian like the steaming pile of junk that it is. No one is, or will, be developing for it. They go in too late and now it is just dead in the water. Too bad Nokia, hope you've learned the lesson of tech, early adopters are the ones who survive.

  9. java. by Lalo+Martins · · Score: 5, Insightful

    Can't tell you why Nokia thinks MeeGo makes business sense. Or Intel. I can tell you why I'll buy it if/when it comes out (and my current phone is an N900): because it's not Java. I can write stuff in Python (comes pre-installed), I can run stuff not specifically written for the platform (emacs, kobodeluxe), I don't have to put up with anything I don't want to. That, for me, is a sell.

    1. Re:java. by DNS-and-BIND · · Score: 4, Funny

      Well, that should certainly win Nokia several million customers right there!

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    2. Re:java. by Anonymous Coward · · Score: 1, Insightful

      My thoughts exactly. I truly hope there's room for one open mobile operating system on the market. The situation would be:

      iOS: closed
      Android: semi open, you are free to develop applications for it in the extend that the java sandbox allows.
      MeeGo: Open source *nix goodness.

    3. Re:java. by Lalo+Martins · · Score: 5, Insightful
      Maybe not. But perhaps it could win them several thousand developers. And then the apps would win millions of customers.

      Or maybe I'm a dreamer...

    4. Re:java. by martyw · · Score: 4, Insightful

      Exactly, MeeGo allows you to code in Python/C/C++/Fortran and even Java/Mono/C# whatever - the GNU GCC is there, standard open source project and libraries all working, just ask any developer, they are loving it. So from the dev's POV it is heaven. Now the marketing, branding and UI of the MeeGo platform -- that is completely other matter..

    5. Re:java. by LWATCDR · · Score: 1

      That is simple. The Infoworld guy and most people have an American viewpoint myself included about Nokia. Nokia is still the biggest cell phone maker on earth.
      In the US they are sell a few super expensive smartphones and a few super cheap phones. If the push out MeeGo it will have a huge marketshare in a flash.
      The real reason for Nokia not being a big deal in the US is that the majority of US cell phones use CDMA vs Europe and many other places that GSM only. Nokia just doesn't have many CDMA phones and Nokia has not make many deals with US carriers.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    6. Re:java. by puto · · Score: 1

      Wrong on both counts. ATT and TMobile are carriers that use GSM in the states. Verizon and Sprint are CDMA. ATT has 93 million subscribers Tmobile has 30 million, and then you can probably lump lump in another 10-20 million of Trac-fone users. I would put around 60% of the market GSM in the states. The reason Nokia lost it's US market share, is because NOKIA refused to play the carrier's game(letting the carriers design and saying what features are allowed on the phones). It also was late to the market with flip and feature rich phones. I would also suggest you look at a US GSM coverage map.

      --
      The Revolution Will Not Be Televised
    7. Re:java. by LWATCDR · · Score: 1

      Verizon CDMA and is the biggest mobile company in the US.
      Sprint is number 3 and is CDMA.
      Verizon and Sprint probably out number AT&T and TMobile. I would put your guess as being off.
      Verizon Wireless (93.2 million), CDMA
      AT&T (92.8 million), GSM
      Sprint Corporation (48 million), CDMA IDEN
      T-Mobile USA (38.5 million), GSM
      TracFone Wireless (15.4 million), GSM CDMA
      MetroPCS (over 7.6 million). CDMA
      US Cellular (6.1 Million) CDMA
      Cricket (5.7) million CDMA
      http://en.wikipedia.org/wiki/List_of_United_States_wireless_communications_service_providers
      So 93.2+48+7.6 + 6.1 + 5.7 =160 millon CDMA users give or take.
      GMS is 92.8 38.5 and 15.4 =146.7 give or take.
      These are rough numbers because some of Sprints users are on IDEN and some of TrakFone users are on CDMA. But I with these numbers I will stand by the statement that majority of US users are on CDMA. And I did say that Nokia had not made many deals with US carriers. The last smart phone from Nokia that I saw offered by a US carrier was the e71x and yes Nokia removed features from it for AT&T. I do agree that not playing nice with the carriers is part of the issue but also not putting any effort into CDMA also I believe hurt them as well.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:java. by jinx_ · · Score: 1

      now if only they'll put some damn memory in whatever device they announce. "1 gig of memory!" does not mean 256mb RAM and 768mb swap. that's probably the biggest thing that annoyed me about the n900. it was outdated on release day. (that and the goofy ass 3 row keyboard. guys... splurge for a digit row for christ's sake. let us use something resembling a true qwerty setup. having to pop open a menu or remap the keyboard is a complete fail. use the g1 if you need a reference.)

      i will be thinking very hard before i adopt meego. if the device is anemic i'll probably just save my duckets and end up toughing it out with maemo.

      --
      jinkusu
  10. Reality check people by dbIII · · Score: 1

    The still sell more phones worldwide than Apple or anybody else and are not going to fold if they take a few more months to ship than expected.

    1. Re:Reality check people by Toy+G · · Score: 3, Insightful

      yeah but their margins are thin and getting thinner by the day. They currently rely on third-world consumers not being able to afford Android or Apple phones, but cheap 'droids are less than a year away...

      --
      -- Let's go Viridian.
    2. Re:Reality check people by phishtahko · · Score: 1

      The won't fold, but they're getting left behind. I love my slow, crash-prone N97 but if they don't have something speedy with a meego paint job by Q3 next year I'm going to have to seriously reconsider not jumping ship to HTC.

    3. Re:Reality check people by Anonymous Coward · · Score: 1, Interesting

      Not cheap 'droids that can survive in those environments. And define cheap? Remember, US smartphones are heavily subsidized by carriers, which doesn't happen nearly ever in third-world markets.

      The battery life isn't 1/100th of what it needs to be (power outlets can be a week apart...Androids spend more time plugged in charging then not, which makes it hard to even call them "wireless devices").

      The devices aren't anywhere near rugged enough. Sand, water, being thrown into rucksacks.

      Android devices require support. Most of these people don't have computers...how do you patch an Android w/o a PC? Phones in these markets are bought on the street, they have to work with basically zero support from anyone, ever.

      It'll be a long, long time before something like a real smartphone will be suitable for such environments. A long, LONG time.

    4. Re:Reality check people by pieterh · · Score: 1

      Well, cheap is $25-$50 for the hardware + whatever the software costs. For Android, that is essentially zero and this makes Shanzai + Android the cheapest possible platform for Africa.

      Battery life: most is taken up by fancy screens, wifi, 3G, GPS. Kill all that for a low-cost phone, stick a solar panel on the back, and the battery will last 2-3 days of real use. Furthermore, it's not a week between power outlets, they're everywhere, they just cost money to use.

      Rugged? Hardly the point. When you earn a dollar a day, you take _really_ good care of stuff costing $24-$50. I've bought 3rd hand phones in West Africa that still worked.

      Patching Android? Are you trolling? I'm on my 3rd Android phone and have never had to 'patch' a phone. WTF are you talking about?

      Bascailly, the parent is right: Nokia is about 12-18 months from losing its low end markets to a tidal wave of cheap Android slabbies from China. I'm predicting they will be bought by some random Chinese firm just for the brand, like Commodore, in three years, max.

    5. Re:Reality check people by MrHanky · · Score: 1

      Nokia made a decent profit again the last fiscal quarter after a short dip in the red, with their average phone being more expensive than before. And if the rumours about Gingerbread's system requirements are true (which is highly unlikely, but feature creep won't make it any lighter), the last cheap Android phones will be running 2.2.

    6. Re:Reality check people by Anne+Thwacks · · Score: 1
      Furthermore, it's not a week between power outlets, they're everywhere, they just cost money to use.There are plenty of African countries where you cannot guarantee electricty more than two or three days a week, maximum, and once a week happens. Its not money, its incompetent/corrupt management, and demand growth faster than infrastructure growth. And a lifestype that does not assume that life depends on electricity, or the government.

      Symbian went too far with lockdown, and has never recovered. Lets hope that the message will get through to some others.

      --
      Sent from my ASR33 using ASCII
    7. Re:Reality check people by neumayr · · Score: 1
      You are aware that Nokia is not just some Scandinavian cellphone shop that could just be bought, right?
      Sure, they might get rid of their cellphone division like Siemens did, if that's what you mean.

      Battery life: most is taken up by fancy screens, wifi, 3G, GPS. Kill all that for a low-cost phone, stick a solar panel on the back, and the battery will last 2-3 days of real use. Furthermore, it's not a week between power outlets, they're everywhere, they just cost money to use.

      Then you don't have a lot more features left, and are in almost direct competition to dumbphones with a battery life of weeks. Which are a lot more rugged, always a good thing no matter how well you treat your phone.

      Rugged? Hardly the point. When you earn a dollar a day, you take _really_ good care of stuff costing $24-$50. I've bought 3rd hand phones in West Africa that still worked.

      Sure, but when you only earn a dollar a day, you want want to use those costly power outlets as little as possible. Refuting your own point there.

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    8. Re:Reality check people by Anonymous Coward · · Score: 0

      That's why you pay money to the guy with the generator for 45 minutes on his power strip.

    9. Re:Reality check people by Barefoot+Monkey · · Score: 1

      I live in the third world, so I thought I should remark on your comment about us.

      Not cheap 'droids that can survive in those environments. And define cheap? Remember, US smartphones are heavily subsidized by carriers, which doesn't happen nearly ever in third-world markets.

      Unsubsidised Android phones are affordable here if that's what you want, but carriers do subsidise phones too. Most people get subsidised phones, and even those work with any carrier.

      The battery life isn't 1/100th of what it needs to be (power outlets can be a week apart...Androids spend more time plugged in charging then not, which makes it hard to even call them "wireless devices").

      Where do you get the idea that power outlets can be a week apart? Either you have access to electricity or you don't. Regarding your assertion that Android makes phones require more time being recharged than not, I'm afraid that I must ask you to provide a citation because I don't believe you.

      The devices aren't anywhere near rugged enough. Sand, water, being thrown into rucksacks.

      How rugged do they need to be? Are you under the impression that third-world cultures mistreat their phones? A phone doesn't need to be any tougher in Ethiopia than it does in the US. Anyway, Motorola makes some very tough phones that come with Android.

      Android devices require support. Most of these people don't have computers...how do you patch an Android w/o a PC? Phones in these markets are bought on the street, they have to work with basically zero support from anyone, ever.

      Are you telling me that Android devices need more support than any other phone? You don't need to patch Andoid phones at all. If you want to then you can take it to a cellphone shop. Didn't you know - here in the Third World we usually buy phones from shops, rather than on the street. You don't even need to take it to the same shop from which you bought the phone though - any one will be willing to patch your phone for you.

      The world outside your comfort zone is not how you imagine it to be.

    10. Re:Reality check people by dalesc · · Score: 1

      There is no such thing as an invulnerable company. It doesn't matter how big they are or how many products they ship. History is full of fallen Goliaths.

    11. Re:Reality check people by Noughmad · · Score: 1

      There is no such thing as an invulnerable company. It doesn't matter how big they are or how many products they ship. History is full of fallen Goliaths.

      Actually, it does. See: http://en.wikipedia.org/wiki/Bailout#US_TARP_and_related_programs

      --
      PlusFive Slashdot reader for Android. Can post comments.
    12. Re:Reality check people by Anonymous Coward · · Score: 0

      Do not underestimate the might of this fully armed logistics machine. Nokia excels at logistics and manufacturing -- this was their main weapon against Ericsson, Motorola and whoever else they've beaten in the market so far -- and their size advantage means it will be hard for the smaller droid manufacturers to beat them with price.

  11. Why? by DMiax · · Score: 4, Insightful

    In my case because there is a market for people that don't want to develop for a dumbed down linux and want a real development environment.

    Also of note the fact that they recently increased the planned releases for Symbian^3 (four phones now on WP) that Symbian^2 phones keep being released in the Japanese market and Symbian^1 is alone probably domnant in the smartphone market overall.

    If they could finally get a Symbian SDK working on linux I would jump on it immediately. Linux needs terribly high specs, Symbian is impressive in this sense and I could easily keep two/three test phones for hobby development.

    But I digress: if the choice is a linux distro and Android I will buy the linux distro, so I can install every possible package I already have on my desktop/laptop.

    1. Re:Why? by benjamindees · · Score: 2, Insightful

      But I digress: if the choice is a linux distro and Android I will buy the linux distro, so I can install every possible package I already have on my desktop/laptop.

      This is such a huge advantage, but the market of people who want it is so tiny no company will ever chase them.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    2. Re:Why? by niftydude · · Score: 2, Interesting

      But I digress: if the choice is a linux distro and Android I will buy the linux distro, so I can install every possible package I already have on my desktop/laptop.

      I completely agree with this. Also - I am hanging out for the ability to do x11 forwarding with ssh. ssh -Y -C will be THE killer app for me. I would have bought a n900 long before now just for this if the handset didn't happen to be such a large and ugly brick.

      --
      You can never know everything, and part of what you do know will always be wrong. Perhaps even the most important part.
    3. Re:Why? by SpzToid · · Score: 1

      Huh? When did you try to run a Symbian SDK on Linux last? I am running QT Creator 1.3.83 on a 3 year old, 300 euro Compaq Presario C700 w/ 2Gb RAM, using 32bit Ubuntu 10.10; and it runs great.

      -> If they could finally get a Symbian SDK working on linux I would jump on it immediately.

      Well now is your chance. Here's some more information for you:
      http://arstechnica.com/open-source/news/2010/09/nokias-cross-platform-development-strategy-evolves-with-qt-47.ars

      --
      You can't be ahead of the curve, if you're stuck in a loop.
    4. Re:Why? by DMiax · · Score: 1

      From that article:

      Availability
      The Qt 4.7 SDK—which includes the toolkit, a build environment, and the Qt Creator development environment—is available today for Windows, Linux, and Mac OS X. Mobile flavors of the Qt 4.7 toolkit have also been released, but the mobile SDK isn't available quite yet. It's a bit confusing, due to Nokia's slightly eccentric branding. The mobile SDK, which is called the Nokia Qt SDK, is not the same thing as the Qt SDK.

    5. Re:Why? by DMiax · · Score: 1

      Replying to myself to clarify: it is completely possible that there is a full toolchain available with which one can build Symbian applications on linux. There were a few unofficial scripts and they have dished out a "remote compiler" service mainly for this reason.

      But there is a huge disconnect where they cannot properly communicate to freelance programmers like me what we have to do to have a supported SDK that will not disappear and be updated for the next Symbian version. I am sure that their commercial partners are well served.

    6. Re:Why? by RichiH · · Score: 1

      In that case, it's a good thing that BMW and Audi are already using Meego for their under development car computers.

      High-end cars is a market worth chasing.

    7. Re:Why? by oji-sama · · Score: 1

      Not sure if this exactly answers your questions, but you should probably check this out: QT for mobile plarforms

      --
      It is what it is.
  12. Why would anyone want Nokia to do something awful? by Anonymous Coward · · Score: 3, Informative

    Android is all cool and stuff, it's also FLOSS and great, and whatever.

    However, it has its shortcomings which make it less than a desirable phone operating system for me. First of all, MeeGo, Maemo and their cousins allow me to run any vanilla GNU/Linux GUI applications. They are most often inconvenient to use on a phone, but they are sometimes better than what's available on the platform. On Android I'm limited to apps written for Android. Thanks but no thanks.

    Also, programming for Android? You need Java or another language that compiles for JVM. Want to program in Python? Good luck. You can't, and you'll never can, because Jython isn't portable to Android. Want to program Ruby? Haha. With non-Android distros I can write an app, run it on my desktop without any additional software installed, and then copy it to the phone as is. And it will run.

  13. meego is much more interesting by hotwax · · Score: 5, Insightful

    The Android phones I've seen are pretty much as locked down as the iPhone. Meego is the only phone OS with some potential for new and interesting things. And Nokia were successful in the first place because they dared to try new things.

    1. Re:meego is much more interesting by asnelt · · Score: 4, Insightful

      You must be trolling. It's not Android that is locked down. It's the phone manufacturers that abuse the openness of Android to lock their phones down. Granted, there are proprietary drivers on every Android phone at the bottom and there are proprietary apps at the top (which can be removed from rooted phones). Moreover, Android itself is developed by Google behind closed doors. But still Android itself is open. That is the reason why forks of Android like the Cyanogen mod can emerge. And this is something that did not even happen with Maemo. On its internet tablets Nokia used mostly FOSS but kept enough closed so that it did not loose control over the platform. For instance 1/3 of the software on the Nokia 770 was actually proprietary. There was even a project called Mamona that tried to replace the closed source components with open source ones and it never reached a stage were it could be called usable. I would say Android has a lot of potential.

    2. Re:meego is much more interesting by Anonymous Coward · · Score: 0

      You're seeing "locked-down" to mean non-modifiable firmware area. I think OP might've meant how the Android userspace is heavily restrictive, forcing you to root the phone to do anything of significance. While that's not a bad thing, Android could have been built to be more flexible. It's more powerful than iOS is at any rate.

    3. Re:meego is much more interesting by Anonymous Coward · · Score: 1, Interesting

      >Android itself is developed by Google behind closed doors. But still Android itself is open. That is the reason why forks of Android like the Cyanogen mod can emerge.

      Well, MeeGo goes a step beyond and you can actually contribute code to it, you can see it being developed in open. In the end, It's all relative: iOS is less open than Android and Android is less open than MeeGo.

      And btw, you can fork MeeGo whenever you want, that's not the case with Android-when you can do a fork only if Google decides to release the code.

    4. Re:meego is much more interesting by Anonymous Coward · · Score: 0

      Except that you can, y'know, install any app you want on an Android phone.

    5. Re:meego is much more interesting by Nerdfest · · Score: 1

      It would be very nice if they licenced it such that the phone carriers can't do to it what they did to Android with non-removable UI features, etc. I hate to say it, but slightly less free in this case would be better, as long as it kept freedom for the user to upgrade more easily.

    6. Re:meego is much more interesting by hotwax · · Score: 1

      I was mostly referring to the user experience. Maemo on the N900 feels like a full desktop OS with real multi-tasking and real software (on a slightly too slow computer), and I am assuming Meego will have similar functionality. Android phones feel like advanced iPhones. Everything is still about "apps" and to do anything fun you have to jailbreak.

    7. Re:meego is much more interesting by Anonymous Coward · · Score: 0

      Ummm...care to back that up with any sort of example? Your statement might be true, but you haven't given any reason for us to believe so.

    8. Re:meego is much more interesting by asnelt · · Score: 1

      Well, MeeGo goes a step beyond and you can actually contribute code to it, you can see it being developed in open. In the end, It's all relative: iOS is less open than Android and Android is less open than MeeGo.

      To call Android less open than MeeGo is rubbish. Software is as open as it can get when it is FOSS. Android is licensed under the Apache license and the GPL. So, by definition Android is totally FOSS. There is nothing that could be more FOSS than something that is already FOSS.

      The fact that Google develops Android behind closed doors is a different matter and doesn't make the released software less open. You can take the current Android release, fork it and contribute code to it just as it was the case for Cyanogen mod and a dozen other mods. That the main developer of the project (Google) works in privacy doesn't change the openness of the software project.

    9. Re:meego is much more interesting by tepples · · Score: 1

      The Android phones I've seen are pretty much as locked down as the iPhone.

      You must be trolling.

      Please assume good faith. Apart from the At Ease-inspired home screen that hotwax mentioned, it could easily be that hotwax lives in an area whose signal coverage is dominated by AT&T, a carrier known for removing the "Unknown sources" option from its subsidized Android phones.

      It's not Android that is locked down. It's the phone manufacturers that abuse the openness of Android to lock their phones down.

      It's the carriers at least as much as the manufacturers. If the carriers in the largest single-language market (the United States) weren't so powerful, at least one phone manufacturer could carve out a niche for itself among prosumers by promoting the ability to gain administrative privileges on your own phone and install community-maintained distributions of the operating system. But unless you're on T-Mobile, the only carrier in the United States to offer plans designed for people who bring their own phones, buying an unsubsidized phone for use in the United States isn't recommended.

    10. Re:meego is much more interesting by rdnetto · · Score: 1

      It's not Android that is locked down. It's the phone manufacturers that abuse the openness of Android to lock their phones down.

      So what you're saying is that for the majority of people, Android is in effect locked down.
      My standard for open is being able to root the device (if you have to at all) in under 30 sec by simply installing an app. If you have to fight the manufacturer/telecom to root it, it's not really open. Replacing the firmware/kernel on the N900 is similarly easy - it has no need to be connected to a computer because it is one in its own right. Let's see you do that with an Android.

      --
      Most human behaviour can be explained in terms of identity.
    11. Re:meego is much more interesting by asnelt · · Score: 1

      Again, that is a deficiency of the hardware and of phone manufacturers / carriers changes to Android and not a deficiency of Android itself. Android is in fact so open that it allows manufacturers to do these nasty things that to Android. It should be the people buying the right Android devices to vote with their wallets for the phones that do not impose those restrictions on the users. You did not even have to install an app to root the Google Nexus One for instance.

    12. Re:meego is much more interesting by Anonymous Coward · · Score: 0

      That the main developer of the project (Google) works in privacy doesn't change the openness of the software project.

      Yeah, for a developer it means a world of difference. The code is open source but the project is not open. A project that works like this (code dumps at release time) basically excludes everyone else from contributing. This has been tried many times and it doesn't work. This doesn't mean that the project is a failure, it just means that it isn't an open project.

      Some people have slightly rosy view of MeeGo openness (Nokia wants to control their platform as well and has historically been very jealous of the UI pieces) but the fact remains: Android is not an open project.

    13. Re:meego is much more interesting by rdnetto · · Score: 1

      You missed the point - what matters isn't the potential the OS has, but rather what capabilities it has in practice. Android should be designed in a such a way that being locked down like that is impossible to maintain, either through legal or technical measures.
      You cannot rely on the free market to solve issues like this, because the majority of people don't understand why openness is important. Openness should be more than an option/possibility - it needs to be a guarantee.

      --
      Most human behaviour can be explained in terms of identity.
  14. Abandoned? by Anonymous Coward · · Score: 0

    They haven't abandoned Symbian. What the hell? Quality of articles is falling...

  15. Handset OS race not over yet... by j_col · · Score: 1

    ...and Android has not won it. There is still iOS, webOS, RIM, BREW, WP7, and probably some others that I can't remember. Why not compete in this fragmented market with MeeGo? Eventually we may settle on a single dominant platform, but I don't think Android will become that platform as it is already fragmented within itself due to OEMs "tweaking" the platform to suit their own product differentiation needs, and Google allowing them to do so. MeeGo, like all of these others, has a fighting chance.

    1. Re:Handset OS race not over yet... by vakuona · · Score: 1

      Android is free to manufacturers. Unless Microsoft has one last surprise under it's sleeve, that $10-20 per phone is going to be significant when (not if) the typical price of a smartphone comes under $100. then it becomes a choice between free and good enough, and expensive and making losses.

  16. Re:Why would anyone want Nokia to do something awf by Anonymous Coward · · Score: 0

    I wouldn't run Ruby programs on my phone anyways. I mean, talk about resource hogs...do you have some kind of magic super phone with an i7 chip?

  17. Too many cooks spoiling the broth by phishtahko · · Score: 5, Insightful

    The only thing Nokia needs to ditch is the bureaucracy. It has way too many divisions each wanting to keep features to themselves. They need to combine their E and N series and have a total of no more that 3 smartphones - entry-, mid- and highlevel. They could go up to 6 models if they offer each of the 3 variants with either touch or touch/slide keyboard, but no more than that. They have to many differing visions because of their different devisions. Having one person in charge is essentially the only way to go, since it gets rid of the in-fighting which is currently sinking them. If you want proof, just look to Apple. One gigantic asshole running the show and in 4 years they've turned themselves into the standard the old guard are playing catch-up to.

    1. Re:Too many cooks spoiling the broth by Anonymous Coward · · Score: 0

      Nokia is very different from Apple. Apple is focused on making less products, and make those few products the best they can be. Nokia is focused in delivering very good phones tailored for every niche they can find, so they need to have many models, each one with software tailored for each type of client or provider. That's the reason Nokia has the biggest market share, and Apple will never have a total monopoly. Apple ignores big chunks of the market by focusing on their target customers, that's what makes them very strong with them. But Nokia is too big to use such a narrow approach; if they want to grow, they need to get to everyone.

      That's the reason they bought Trolltech and they are throwing all their efforts on Qt: it is the best tool available to create a platform you can adapt to any device, with any OS, in any market. Java and other VM are the next best, but all of them are controlled by other people (Java by Oracle, .NET (and Mono, since it is a clone) by Microsoft, Dalvik by Google). And no VM is going to be as good for fast graphics as C++.

      I think they are into something. Are they gonna end with Apple's reign? I don't think they are really going after the same markets. And Android's? Android main trouble is fragmentation; Nokia will have a complete control of its platform, so theoretically they could avoid that; but history shows that they have been very bad at that. Time will tell.

    2. Re:Too many cooks spoiling the broth by Compaqt · · Score: 1

      The thing is, I could live with many phone models, if Nokia had a policy of making one phone to rule them all, with a superset of features.

      The way it is now, some phones have some of the good features, others have others. The consumer is left in a quandary, and sometimes that just means he waits it out.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
  18. I recently had to replace my phone... by tuxedobob · · Score: 1

    ... and it annoyed me to no end that I couldn't just get something like my old phone, a Nokia 6150. All the phones now either flip or slide, and are chock full of "features" which are really thinly-veiled attempts to get you to cough up more money for a data plan.

    I just wanted a regular phone with a 12-key number pad that could send text messages with predictive text input. Nope. Not offered anymore. Hell, I can't even send an email to someone without using a data plan and some email "service". (On the Nokia I could simply set an email address as the recipient of a text message.) And one of the features about it I really liked—the ability to set "profiles", multiple preference sets for ring volume and the like—isn't on the one I have now. But dammit, I can take pictures and... not do a whole lot with them.

    And even the 6150 doesn't have something my original cell phone did that I gave up in 2004... I miss Snake. :(

    1. Re:I recently had to replace my phone... by Anonymous Coward · · Score: 0

      Sounds like you're describing the Nokia 1200 series. It's a mobile phone. You call people or send SMSs. That's about it.

    2. Re:I recently had to replace my phone... by phishtahko · · Score: 1

      You don't seem to have looked very hard. The Nokia page on GSM Arena is packed with phones meeting your specifications.

    3. Re:I recently had to replace my phone... by zoney_ie · · Score: 1

      That's not true. Nokia still have a lot of these phones and in candybar form-factor too. Admittedly mostly they aren't offered by ordinary carriers, but I have seen them in real life being offered by Tesco Mobile (if you are in the US, Tesco is a major UK grocery/everything monopoly like Walmart). They cost something like €20 or €30 (that's without signing your life away on network commitments as well!) Mostly the only issue with these (and why people don't go with it) is that it is targeted at the bottom end of the market (even O2 offer sim-only bill contracts of just €15 a month, and you can get very cheap phones with more functionality too - say at €50 price point, so Tesco is for people *really* wanting to spend almost nothing).

      Anyway, the Internet is your friend as it is surely trivial to find a "dumb phone" online cheap (Hong Kong is probably a good bet - postage from there is cheap). Here in Ireland, if you manage to buy something less than €23 there is no VAT or import duty. It's probably the same where you are - i.e. buying something really cheap from Asia there are no hidden extras to pay.

      ----
      2010: 11 years after euro introduction slashdot still can't process the euro symbol character entered directly into the submit form. Pathetic.

      --
      -- *~()____) This message will self-destruct in 5 seconds...
    4. Re:I recently had to replace my phone... by BorgDrone · · Score: 1

      Nokia, SonyEricsson, LG and Samsung are making boatloads of phones like that.

    5. Re:I recently had to replace my phone... by RichiH · · Score: 1

      Nokia 1616
      Nokia 1800

      Have fun :)

    6. Re:I recently had to replace my phone... by sznupi · · Score: 1

      Or C1-00; only a slight change to 1616, but seems to come with much bigger battery. Suffice to say, standby times are insane.

      --
      One that hath name thou can not otter
    7. Re:I recently had to replace my phone... by RichiH · · Score: 1

      At least in Germany, I can only get the C1-01 and C1-02. I haven't looked at the cheapo phones in ages, but I will buy a phone for 27c3 & Fosdem and their home-baked GSM networks.

    8. Re:I recently had to replace my phone... by sznupi · · Score: 1

      Not much better here, across the Neisse and Oder - with Nokia S30 phones (and other similarly simple ones) basically at most included in some prepaid packs, when it comes to "official" channels.

      C1-00 being barely available anyway, just few auctions and ridiculously overpriced for now (~2x 1616) - which seems to be a common problem for such simple phones, when new they are very closely priced to some decently nice S40 handsets (C1-01 for example - also quite basic & straightforward; not really destroyed by inclusion of GPRS & j2me (Opera Mini, IM), simple camera or radio & mp3 player functionality ... bringing greater affordability of those features). Though TBH, even if EU prices of cheap handsets don't follow the "trademark" ones, I'm probably also spoiled - with price differences in those ranges merely appearing negligible to us.

      However, IMHO, if you're looking for something - 1100 is the benchmark, the ultimate lowest-end :) (plus, since almost certainly available only in used state, its prices seem more appropriate(*)). Also the last one not borked by pointless inclusion of 4-way D-pad, which only gets in your way in S30 - 1100 has just bi-directional up&down, what the S30 UI was meant for... (arguably, the same still applies to S40)
      Plus "the world's best selling phone" & "best selling single type of electronic consumer device in history" have a nice ring to it, give it a nice status.

      (*)Hopefully not influenced anymore by the hoax about suitability (of German-made ;p ) 1100 to some supposed firmware modification allowing serious sms fraud...

      --
      One that hath name thou can not otter
  19. It had it coming by Teun · · Score: 1
    Symbian has had it's time but is too limited for future hard and software.

    Android is good because it has a Linux background meaning there is a lot of experience with it yet it's ever more fragmenting.

    So I find it entirely logic that the largest phone manufacturer bites the bullet and goes with a much more mainstream fork of Linux.

    With the success of ARM-bases processors in mind it might be somewhat dangerous to get too cosy with Intel but hey, they already have experience with the other Linux offshoot Maemo on the excellent ARM powered N900.

    Porting existing software to Maemo or Meego is going to be a breeze compared to the many versions of Android.

    Anything Windows is for obvious reasons not acceptable, a phone manufacturer like Nokia would have to fall on really hard times before selling out to Microsoft

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    1. Re:It had it coming by gbjbaanb · · Score: 1

      Nokia would have to fall on really hard times before selling out to Microsoft

      and they don't need to. The E7 phone can work with Microsoft Office documents better than Word does, and you can even create powerpoints on the thing (no doubt to send to your PA with instructions to 'just tidy up the edges', but if you're targeting sales account managers and the like, this is the kind of thing that makes them sit up).

      So why would they 'downgrade' themselves to sell out to MS. In the mobile world, they *are* the Microsoft (in market share, not in bullying uselessness). Microsoft would do well to sell out to Nokia and licence Meego or Symbian. :)

    2. Re:It had it coming by dr.newton · · Score: 1

      While it's true that Android runs linux under the hood, you don't encounter linux at all while developing for Android, or while using it. Thus, the fact that it is based on linux is irrelevant from the perspective of developers and users having experience with it.

      If Nokia does a good job with Meego, it will be just like Android: the linux will be there, and you can get at it if you want to, but developers and users shouldn't have to know or care to be satisfied with the platform.

      These vendors choose linux to use for their OSes not because people know linux, but because they get a lot of stuff for free compared to writing an OS from scratch.

      --
      Just another proletarian malcontent.
  20. And Symbian Foundation is not Symbian. by sznupi · · Score: 5, Insightful

    Seems the news is just that the Foundation might not continue operating in its current legal framework (which depended on few other entities apart from Nokia, and now that they are gone...). But that doesn't lead to S^3 effort ending, as TFS claims (S^4 apparently is, somewhat - only in the sense that, instead of one big future release, its features will be pushed gradually to existing devices; a change for the better IMHO)

    Symbian isn't going anywhere - it has greater share of sales than the next two players combined; when taking number 2 player out of the equation, greater share than all what's rest combined. Might very well be the first smartphone platform to break the barrier of 100 million devices shipped annually, this year.

    All this ignoring the modus operandi of Nokia. Is S40 dead? (checking...) No, it's the most widespread mobile phone platform in the world. Heck, even S30 sells quite a few units. Symbian will be around for a long time, just in price segments where S40 was for large part of the last decade.

    Those segments aren't going away. If anything, the market seems to be getting more diverse than the simplistic "everybody will want either 'true' (for the current definition of 'true') smartphone or something ultra low cost" - but it's probably hard for pundits in few atypical (but highly visible) markets to notice some crucial segments; most of those people have smartphones...

    Smartphones which still sit at around 20% of total shipments. Have been sitting close to that for a few years. People are generally happy with slick UI, touch screen, good web browsing (heck, Chinese makers are starting to integrate even full Opera Mobile), few widgets - "smartphone" doesn't need to enter the equation, as fabulously popular "feature phone" touchscreen mobiles from Samsung and LG have shown recently (those phones from Samsung are why they might be level in marketshare with Nokia by the end of the year, not smartphones)

    As for Android...heck, who knows. Though probably "MeeGo-fied/Qt-fied", to share at least their custom apps with Symbian, to have the same widget engine available (the W3C one, iirc). But they are profitable, in Q3 their revenue has risen, at #1 marketshare it doesn't make sense to willingly get relegated to the status of PC makers (vs. MS/provider of OS). Why Samsung pushes also bada OS (indeed almost a direct continuation of their wildly successful TouchWiz handsets). BTW, funny how MediaTek was apparently almost blocked for some time from participating in Android, by Qualcomm; funny times ahead, now that MT releases their solution for Android soon.

    --
    One that hath name thou can not otter
    1. Re:And Symbian Foundation is not Symbian. by Anonymous Coward · · Score: 1, Interesting

      Alternative interpretation of these announced changes is that Nokia is gradually closing down its Symbian product line and soon Nokia's only own smartphone OS would be MeeGo. Regarding that "one constantly evolving" Symbian platform: Yes, Symbian could be still be around and evolving, just like the Windows XP is constantly evolving with its (security) updates. Yes, outside the US Symbian is still, by far, the most popular mobile OS. But strategically Nokia focuses on gaining more success on US smartphone markets. It is doubtful if even that "constantly evolved" Symbian is enough for winning a significant market share. So, maybe the strategy is now to consider Symbian strategically dead (like XP) and see if MeeGo can do better."

    2. Re:And Symbian Foundation is not Symbian. by rtfa-troll · · Score: 5, Insightful

      Symbian isn't going anywhere - it has greater share of sales than the next two players combined; when taking number 2 player out of the equation, greater share than all what's rest combined. Might very well be the first smartphone platform to break the barrier of 100 million devices shipped annually, this year.

      The thing about Symbian is it really doesn't seem to be going anywhere; in the other sense. The other smartphone OSs; Android and iOS, and even Maemo/Meego, are designed to establish platforms. New Symbian versions consistently fail to run software from old versions. Symbian phones always seem very locked in; for example it used to be difficult to just connect the phone and directly access the whole of it's file system (at best you got a few specific directories). I think that's improved now, but similar stories apply all around. etc.

      What this means is, that the number of symbian devices is irrelevant. Even if Gartner's numbers are a bit exaggerated, it's clear most of those devices are not selling software; are not being used as smart phones and just don't count. Your addressable market for smart phone applications (the main meaningful thing about a "smart phone") is not the number of phones, but the number of phones that are actually being used in a smart way. This determines the amount that other people are investing in the platform and so it's long term future value.

      Nokia could fix this by making sure that it delivered software updates for it's old phones and ensuring backwards application compatibility. This would mean that it would only support one software version over all it's phones and would mean that Symbian apps would become much more valuable. I'd assume, though, that there's something in Symbian or in the way Nokia uses symbian. which makes this impractical.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    3. Re:And Symbian Foundation is not Symbian. by gbjbaanb · · Score: 1, Redundant

      The thing about Symbian is it really doesn't seem to be going anywhere; in the other sense

      You could say the same thing about Windows. Saying it still won't change the world for quite a few years, don't be fooled into thinking the entire world now wants Android phones (good though they are). Incremental updates and a vast target market will keep them relevant for a long time.

    4. Re:And Symbian Foundation is not Symbian. by Anonymous Coward · · Score: 2, Interesting

      Smartphone unit sales out of global mobile phone sales accounted for 10 percent in 2007, 11.4 percent in 2008, and 14.4 percent in 2009. They haven't been holding steady at 20 percent market share since 2007. That doesn't even compute with the addition of new players iPhone and Android. Do you think purchasers of those devices only cannibalized from RIM and Symbian?

      Smartphones had 18 percent year over year growth in 2008 and 25 percent in 2009 compared to an overall slight decline in total mobile phone shipments.

      In 2009, smartphone sales tallied 174 million. This year, they are projected to sell around 270 million units which would account for ~20 percent of the total mobile phone market. It's very impressive growth.

    5. Re:And Symbian Foundation is not Symbian. by aliquis · · Score: 1

      Whole /. article reads like a troll post to me.

    6. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 2, Interesting

      Don't forget to mention the projections from, IIRC, around 2007 telling how they were supposed to be at around 35% right about now. The growth is quite gradual, and like that for many years (might look slightly different from the perspective of few atypical markets which were previously mostly deprived of smartphones by carriers and fed with very locked down handsets)

      Of course, it would help if we had any sensible definition - given how SE A200 "feature phones" have even full multitasking for several years, or how latest S40 also gives a lot...

      --
      One that hath name thou can not otter
    7. Re:And Symbian Foundation is not Symbian. by Splod · · Score: 0

      Seems the news is just that the Foundation might not continue operating in its current legal framework

      This has long been a possibility. But I've heard rumours of a Second Foundation.

    8. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 2, Interesting

      But that's again trying a bit to define what we're looking at in a way which results in a very narrow view.

      How many years do we hear "symbian is dying" while it consistently ships most units and gains most sales, in number of handsets, year after year? ("percentage of growth" might be deceiving when one player is much closer to the absolute limit of "number of all mobile phones sold" than the rest) Oh, "but they aren't used how I say they should be!"? What?...

      It won't matter much anyway when the smarthphones will settle again on some common functionality (on which "feature phones" are settling too, BTW, being used in a smart way; blurring the lines even more). Look what happened with desktop. Browser (covers games, too...), audio/video/photo management, IM, maybe some social networking app in the tray, office; people don't use custom UI for every webpage, custom UI for every radio station, custom UI for every audiobook, custom UI for every e-book - things which dominate some appstores...

      (and seriously, Symbian phones seem very locked, out of all other choices? Claims of incompatibility also seem overstated to me, in comparison; not to mention how many segments Nokia continuously covers)

      --
      One that hath name thou can not otter
    9. Re:And Symbian Foundation is not Symbian. by zippthorne · · Score: 5, Insightful

      I'd assume, though, that there's something in Symbian or in the way Nokia uses symbian. which makes this impractical.

      Indeed there is: cell companies adopted a strategy early on of "never, never, never deliver software updates to old phones" where "old" is "already purchased." If your phone didn't have annoying bugs in it, what would encourage you to get a new one after the 18-24 month financing deal was up, and lock in a new plan?

      In a sense, their "software update" plan has always been, "buy a new phone"

      --
      Can you be Even More Awesome?!
    10. Re:And Symbian Foundation is not Symbian. by Ecuador · · Score: 1

      Exactly. My company was developing for Symbian (among various platforms), and after years of trying to keep up withe various incompatible OS releases while not leaving the numerous previous gen devices out of the loop, at the Symbian 9 release we have up. Porting our app collection would require way too much effort due to the significant changes and it that effort would be squared if we also wanted to keep supporting the 90%+ (at least for a while) of symbian phones out there that could not run the new versions... I mean, what is the point of having that closed ecosystem with signed apps and everything, and specific phones running specific versions of software WITHOUT A FRIGGIN' APP STORE??? No, I am not talking about copying the Apple App store that came years later. The idea was an old one, with a successful implementation. I am talking about BREW (US /.ers should know it) which was working over a wide variety of non-smartphone level hardware, so it should have been much easier for Nokia to set it up for their own devices.
      And to add insult to injury, in 2005 Nokia released the 770 "internet tablet" with Maemo, I got one for our company to evaluate possible developing on it. I remember saying that it was idiotic to keep on pushing with more incompatible Symbian iterations instead of working on that wonderful platform they had and make it friendly enough for a phone. Well, it turns out they being idiotic and they sort of found out 5 years too late. Although they are still not dropping Symbian, at least they are giving MeeGo a try. Can you imagine what they would have done by now had they been developing Maemo phones for the last 5 years? They would probably have had an answer to iPhone... RIGHT BACK THEN when the iPhone was launched!

      --
      Violence is the last refuge of the incompetent. Polar Scope Align for iOS
    11. Re:And Symbian Foundation is not Symbian. by Anonymous Coward · · Score: 0

      We have the data for the first three quarters of 2010. Projecting the fourth quarter is much easier than making market predictions three years from now. Mind you that 2008 and 2009 was amidst a global recession, but people still forked over money for premium smartphones and more expensive service plans while feature phone sales were down slightly overall.

      Smartphone year over year growth rate
      2008 18%
      2009 25%
      2010 55% (with Q4 projected)

      There is no personal technology device where that type of growth rate would be classified as "quite gradual."

      Good day.

    12. Re:And Symbian Foundation is not Symbian. by rtfa-troll · · Score: 1

      But that's again trying a bit to define what we're looking at in a way which results in a very narrow view.

      Absolutely; but I'm trying to show that that view is the one which tells us most about the future. In other words; I'm defining the "smart phone" market separately from the "feature phone" market; with a separation between people who use a phone for calling and have a few other useful things and people who have a mobile communication application platform with them which they are gradually building more and more uses for.

      How many years do we hear "symbian is dying" while it consistently ships most units and gains most sales, in number of handsets, year after year?

      I think you want to look at the reason for those continuing sales. This is simple. Symbian ships more because if you want to get a top end Nokia, you have to get Symbian. If you want to get a solid phone with a good camera or good multi-media or etc. etc. often you really want to get a top end Nokia. Most of the time, you try another brand and really really regret it. Then you get a Nokia one more time.

      If Nokia can get those people who have Symbian phones to use them as smart phones, even if they bought them whilst not caring about the "smart" then Nokia's future as a smart phone company is guaranteed. The problem is that it seems that Symbian has been inadequate for that. The people never notice the fact that it's "smart" and never start learning to use that. Those same people are beginning to notice that iPhones and Android phones do something useful. They will end up buying those to do things that their old phone was capable of, but they just didn't know about it. That is a marjor Symbian failure and if Nokia doesn't fix that, that will fix Nokia.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    13. Re:And Symbian Foundation is not Symbian. by Anonymous Coward · · Score: 0

      As an ex-nokian I know that S40 will run on top of a mobile linux platform, I have seen it working. Nice stable S40 apps, familiar look'n'feel, etc. And anything new can be a native linux app, with an S40 icon/menu option.

      Users will not notice a difference but will be slowly migrated to the new platform. The in-house S40 development team can begin training in developing linux apps by porting the S40 apps.

      Slowly retire the S40 platform, keep users happy, have a motivated development team learning new stuff, have only 1 mobile OS across the whole range of phones. No more messing with S30, S40, S60, S90, Meego, etc.

      Makes manufacturing easier if every device has the same kernel. All prod tests done with only kernel loaded. Customer/region/device specific software only loaded prior to shipping. Maximise flexibility while reducing costs.

    14. Re:And Symbian Foundation is not Symbian. by Anonymous Coward · · Score: 0

      Fanboi much?

    15. Re:And Symbian Foundation is not Symbian. by tepples · · Score: 1

      Browser (covers games, too...)

      Browser doesn't cover games easily if a browser's DHTML rendering or 2D canvas or what have you is too slow to run even NES-class graphics in real time. Nor does it cover games if the browser's offline support isn't rich enough to avoid using kilobytes of the phone's data plan every time the game starts.

    16. Re:And Symbian Foundation is not Symbian. by Anonymous Coward · · Score: 0

      That's crap. My last 2 Nokia phone have always had updates available and can download and update the phone automatically via OVI too.

      I can also understand how backwards compatibility is hard as the nature of the phone is changing but there are quite a few apps that work on the N95 to N97 quite happily.

    17. Re:And Symbian Foundation is not Symbian. by Rexdude · · Score: 1

      Symbian phones are locked in? Are you serious? The concept of a jailbreak does not exist for Symbian phones because you can do whatever you want with them. Every phone has supported Mass storage mode for the memory card for at least 5 years now. The only reason to hack a Symbian phone would be to add your own self signed certificate to the keystore if you explicitly want to run pirated software which won't install without a valid digital signature. A very small fraction of people need to do this- for the majority of users, all features of the phone work perfectly fine unlocked out of the box. You don't need an iPhone style jailbreak to enable tethering or Bluetooth file transfer or what have you- all these things are available right away.

      --
      "..One hosts to look them up, one DNS to find them, and in the darkness BIND them."
    18. Re:And Symbian Foundation is not Symbian. by cbope · · Score: 1

      Interesting, have you ever actually owned a Nokia? I have owned many different Nokia models over the past 10+ years and nearly every one received multiple software updates during its lifetime. Only the oldest S30-based rarely got updates, and that was because it was simply a phone. It made calls. It stored my contacts. Not much could go wrong. My latest S60-based E75 which is a bit over 1 year old is on its 3rd software update. I would say in the past 5-6 years every Nokia smartphone I have owned has received at least 3 software updates over its usable lifetime. The updates fix bugs, improve stability and add new features. The last update for my E75 even improved UI responsiveness.

      Or maybe you are talking about the *operators* not delivering software updates for the subsidized phones they sell? I don't believe it's the manufacturers not delivering on updates, it's the operators. And it's very likely because they have customized OS loads on their phones to disable features they do not want to support. Tethering anyone?

    19. Re:And Symbian Foundation is not Symbian. by Snaller · · Score: 1

      "Symbian isn't going anywhere"

      Except going straight down. If the current trend holds Android will have outpaced it in 3-4 years.

      --
      If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
    20. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      That was about desktop / PCs. Doesn't need to be exactly like that on mobiles; but with HTML5 "offline" capabilities - why not? And Flash on mobiles essentially has such capability already - one of the kinds of apps of few non-smartphone platforms are flashapps.

      And anyway, the point wasn't how nothing will be a local app ("even" feature phones have their flavors of those too, after all), but how some platforms took the concept way overboard (while using those meaningless numbers in PR)

      --
      One that hath name thou can not otter
    21. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      With the last data available, it had biggest gains in the number of units shipped. "Percentage of growth" is a bit deceiving, greatly depends on the current position in the market (high marketshare diluting this measure of gains); and with ceilings hidden.

      Unless of course one subscribers to the view that exponential growth in a finite world can go on forever...

      --
      One that hath name thou can not otter
    22. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      That assumption is simply not strictly true. Nokia does give updates; the new Symbian Qt SDK supports phones which are 4 years old at this point. S^1 devices basically got S^2 through gradual updates.

      There are limits of course - and with good reasons, considering how rapid the improvement of mobile phone hardware was for the last decade+ (or, alternatively, how that progress went towards lower prices for barely more capable hardware, which doesn't leave much room for better software). That might be only nearing to an end (in the sense of hardware getting "good enough"), and only in some segments of the market (ironically, those most often upgrading phones)

      What you're saying, is in large part about some carriers.

      --
      One that hath name thou can not otter
    23. Re:And Symbian Foundation is not Symbian. by tepples · · Score: 1

      That was about desktop / PCs.

      Which aren't always online either. Some areas still not served by cable or DSL must use satellite or 3G, both of which have monthly transfer caps. Other areas (such as where my mother lives) have DSL, but it's PPPoE, and people can't get an IP address if enough other customers in the same neighborhood have an IP at the moment.

    24. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      How is that relevant, when drawing analogies with mobile phones, in the context of appstores with custom apps for every little thing which can be handled by web browser (vs. custom apps for accessing one webpage) or universal internet radio application (vs. one app for each radiostation)?
      Yes, some things are better as a local application, I'm not saying they're not; just that "huge library of apps" is an aberration. And demonstrably so also on a PC; where, even in the case of games, large part happens in the browser nowadays (which is an example)

      --
      One that hath name thou can not otter
    25. Re:And Symbian Foundation is not Symbian. by tepples · · Score: 1

      How is that relevant, when drawing analogies with mobile phones, in the context of appstores with custom apps for every little thing which can be handled by web browser

      A custom app is stored in a dedicated area in the phone's memory. A web app is stored in a smaller area called the cache that will be emptied once there are enough other items, and once it's gone, the app is unusable until the user turns the handset's data connection back on.

      Yes, some things are better as a local application, I'm not saying they're not

      So let's quantify which are. Browser-based apps will reduce the need for local apps as user agents come to support JIT compiling of JavaScript, the 2D canvas, WebGL, localStorage, and explicit caching. But with so many deployed handsets still officially stuck on Android 1.x, I don't see that happening too quickly.

    26. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      Really, a custom app for accessing web page keeps the data in a dedicated area in phone's memory? Custom app for accessing one internet radio station fetches the stream from local flash, too? There is a difference between an e-book file or audiobook file opened in suitable universal application vs. an e-book packaged as singular app, or audiobook packaged like that?

      That is what very large part of appstores have become. This is the kind of useless multiplication of efforts rampant also on Android 1.x (though it's not the worst of course), which doesn't show at all how "application ecosystem is crucial."

      And it has some relevance to games, too; doesn't need to fully follow on every point of an analogy / feature phones can have local apps, too (yes, typically not so integrated, not fully multitasking - but it's not much of a problem for games)

      --
      One that hath name thou can not otter
    27. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      How long ago was the 8 to 9 shift? And now Qt is the only recommended way, supporting 4 year old phones.

      Completely dropping Symbian in favor of Maemo Nokia would more than nullify the advantages of the former - remember how large those early Maemo devices were, and with how short battery life? NVM how it would ignore their modus operandi - vast spectrum of device classes and pricepoints; Symbian goes where S40 was.

      --
      One that hath name thou can not otter
    28. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      S40 is the "feature phone" platform running on very lightweight internal RTOS and modest hardware - I doubt using it on top of heavy kernel would be a good idea for this class of devices, or indeed that it can do that...
      And it would mean abandoning lower price segments.

      --
      One that hath name thou can not otter
    29. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      Yes, you chose the most impressively looking number. Without keeping it in the context of growing sales for all mobile phones.

      --
      One that hath name thou can not otter
    30. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      Did Nokia close down S40? Even S30 is going strong... Both strategically important, don't listen to the pundits caressing their new wave of smartphones, that I mentioned.

      --
      One that hath name thou can not otter
    31. Re:And Symbian Foundation is not Symbian. by Anonymous Coward · · Score: 0

      How long ago was the 8 to 9 shift? And now Qt is the only recommended way, supporting 4 year old phones.

      It was long ago, but not long before that was the smaller jump from OS 6, which still was work for developers, then while you say that QT works on 4 year old phones, the SWITCH to QT for developers is more recent (around 2 years ago IIRC?), so whoever had invested a lot of effort in porting for OS 9 and later would need even more work if they wanted to switch to QT. In any case, QT was too little and WAY too late, too many devs have been burnt over the years to bother. Oh, and as I said the other problem was the app distribution issue. There was the BREW paradigm to follow, but no, again the OVI store was too little too late.

      Completely dropping Symbian in favor of Maemo Nokia would more than nullify the advantages of the former - remember how large those early Maemo devices were, and with how short battery life?

      They were not intended as phones. They had full keyboards, huge screens etc. The iPhone (a unix-based OS phone) hardware was anything but exotic even when it came out (half-VGA display? puhh-leeze), I am sure Nokia could build a Maemo phone had they devoted effort on Maemo for phones back then.

      NVM how it would ignore their modus operandi - vast spectrum of device classes and pricepoints; Symbian goes where S40 was.

      Symbian is a smartphone OS. There are millions of S40 customers who can afford a smartphone, BUT DON'T WANT a smartphone. It would be idiotic to try and force Symbian on to everyone.

    32. Re:And Symbian Foundation is not Symbian. by sznupi · · Score: 1

      Yes, it was long ago and previous jump was smaller, as you said; and at the time of its cradle ("too little too early"?) / now they weren't supposed to change from something still limited and very close to S40? The "switch" to Qt happens just now - but old-style apps are still working, it's just a recommended way forward; and still functioning on 4-year old phones. Ovi has apps and growth as it is anyway.

      iPhone is not a good example, it had a barely better battery life from Maemo tablets...

      So forcing Maemo, eliminating devices between it and S40, wouldn't be similarly idiotic?... (and you know, those people happy with S40 can just continue to get them, just less expensively for example; you can still buy S30, tons of people do)

      --
      One that hath name thou can not otter
  21. Because it is real open source by Anonymous Coward · · Score: 0

    And some people see real value in open source. It seems many slashdotters (of all the people) don't know the benefits of a completely open system that doesn't rely on a company but a global community that builds on each other's work. No such thing as security through obscurity. Applications and practises from the Unix world can be used, often without any modifications. You can already run a Debian distro concurrently with the current maemo for the N900 (no reboot, a simple chroot is enough) just in case you need apps from the debian repos instead of the offcial and unofficial maemo ones. Some pople just value the freedom to choose over the convience factor. For those there fortunately is maemo/meego.

  22. Re:Why would anyone want Nokia to do something awf by XDirtypunkX · · Score: 3, Informative

    You might want to look into the NDK on Android. It's perfectly possible to port a runtime written in C/C++ to Android and then use that to run your python code.

  23. Sure is some FUD here by ceeam · · Score: 1

    a) Symbian foundation "shutting down"? Well, sure a [citation] would help.

    b) Even if so - it was of only so-so use for Nokia. They are basically the only Symbian developer worth anything. FLOSS Foundation spin-off shutting down does not mean that Nokia won't continue it.

    As for Symbian itself - it's not that bad. It lacks some polish. Well, seriously lacks, including the infra-structure. But it has some nice feature - like ability to run native code which Android badly misses (some poorly-informed guy should post here about NDK, but it's not it at all). And I, for example, won't ever be programming in Java anymore, thank you. Symbians should just drop the certificate bullshit to get developers interested again.

    1. Re:Sure is some FUD here by sznupi · · Score: 1

      With some recent changes on Ovi Store, the certificates thing can be now done for free and speedier.

      --
      One that hath name thou can not otter
  24. Bad Journalism by valdyn · · Score: 5, Insightful

    Very badly researched articles and Summary:

    Symbian Foundation closing does not imply that Nokia will stop Symbian Development.
    Symbian 4 being transformed from an incompatible system into an upgrade path from Symbian 3 does not make it go away except for the name.
    And another one:
    "Symbian 3 made it onto a couple of phones, but no one really noticed or cared"
    The first Symbian 3 device was only just released (N8) and reviewed by the usual websites, and 2 more are announced and prototypes released and shown at the Nokia Fare (C7, E7).

    I'm to lazy to actually read the whole articles but there's probably more nonsense.. bad Journalism.

    1. Re:Bad Journalism by Anonymous Coward · · Score: 0

      Its not just bad journalism its a FUD campaign from apple and/or google. I think they are scared because n8 is selling rather well.

    2. Re:Bad Journalism by Alex+Belits · · Score: 1

      Judging by obviously inadequate Windows Phone 7 mentioned in it out of the blue, it's from Microsoft.

      --
      Contrary to the popular belief, there indeed is no God.
    3. Re:Bad Journalism by js3 · · Score: 1

      Why would microsoft suggest they switch to Android? The article is poor and borderline flamebait. It starts with a falsehood, suggests a swtich to android, then throws in a completely irrelevant "copy and paste" windows 7 issue in there. Terrible article.

      --
      did you forget to take your meds?
    4. Re:Bad Journalism by sznupi · · Score: 1

      Well, it seems to suggest switching to WinMob7 it one place...

      --
      One that hath name thou can not otter
    5. Re:Bad Journalism by 21mhz · · Score: 2, Insightful

      I especially liked the tidbit on how MeeGo "made almost no headway after several years."

      The reality says that it was announced in February this year, and is near its first platform release with Nokia contributions and touch support.

      --
      My exception safety is -fno-exceptions.
    6. Re:Bad Journalism by DTemp · · Score: 1

      If you call this a "review from a usual website," Gizmodo basically said the phone was so weak and has such a little chance on the market, that they weren't going to review it. http://gizmodo.com/5667723/why-were-not-reviewing-the-nokia-n8

  25. Symbian is dead? by drolli · · Score: 4, Insightful

    a) News of symbians death are IMHO highly exaggerated. I right now would place a bet that symbian OS will be a significant palyer in the market for the next 5-10 years (maybe more). Why? Go to Indonesia, China, Malaysia, Africa, Russia etc. many people there dont afford iphones, but low-end Nokia devices are pushes out in numbers you cant imagine. And the current mid-class devices (e.g. Nokia e63), which you can already buy there will be the next low-end devices. So - taken into account the fact that Nokia can build successfully push out phones counted in 10s of millions and be profitable on a much smaller margin for revenue, you think they should experiment around?

    b) Android: Nokia stayed away from bundling the devices with services from other companies, because then you would invest in developments where somebody else dictates the rules. So should Nokia accept to help advertise and develop a platform, which makes them googles slaves? As a happy Nokia customer i say: No.

    c) customer base: If it want something for playing i'll buy and additional android device,iphone,psp or wii. If i want a workhorse, i'll buy the next Nokia phone - if possible a symbian one. I have all the software i need for it, namely dictionaries, pim tools, mail client, podcast downloader, internet radio, youtube client, skype, messaging clients, google maps (and nokia maps), office documents editors. Moreover it runs java programs. This is my definition of "what do i primarily need?". I wont sacrifice running this stably for an unknown gain in other things.

    So to say it shortly - the customers interested in having a cool looking web-surfing device Nokia already are lost for Nokia. Their potential customer base are people who want a cheap phone or something which "just works", with a little hooks as possible. For that they should take their time and keep the keys in they own hands.

    1. Re:Symbian is dead? by t2t10 · · Score: 1

      As a long-time (ex-)Symbian user, I have to say: it just doesn't cut it anymore. Too many things on Symbian just don't work right: OTA syncing, web browsing, Ovi, pen input, even locking the phone. Now that Android also has tethering, there is no reason to stay with Symbian.

    2. Re:Symbian is dead? by puto · · Score: 1

      I agree. I bought an E-63 a few months ago for all of the reasons you listed. I live in Colombia and when I moved here I came with a Samsung Blackjack that was showing its age after four years. I wanted a new smartphone but I needed the ability to find chargers and batteries all through out Latin America. And to just work. Nokia was the only choice. And I have to travel all over latin america, everyone here has a candy bar nokia.

      --
      The Revolution Will Not Be Televised
    3. Re:Symbian is dead? by drolli · · Score: 1

      About which phone are you talking? My E61 (bought in 2006) and my E63 (bought 1 year ago) both are fine (besides the pen input, which i did not try yet).

      The web-browsing works fine with opera mini/mobile, and even the build-in browser is not terribly bad.

    4. Re:Symbian is dead? by puto · · Score: 1

      Really? I Have an e63 and browsing is fine, and if you dont like the nokia browser, you can install Mini Opera. I have never had a problem with the OVI store. The phone locks and unlocks fine. A great feature rich phone for a low prce.

      --
      The Revolution Will Not Be Televised
    5. Re:Symbian is dead? by t2t10 · · Score: 1

      Well, I have had problems with web browsing: some sites don't work, for others, it's hard to hit input fields and buttons. Opera Mini doesn't solve those problems. Phone lock is cumbersome and requires at least three clicks. And the phone gets confused and becomes hard to unlock when there are notifications and code locks. Etc.

      It's not that Symbian phones are complete disasters, but they are cumbersome and limited compared to a modern Android phone and not much cheaper.

    6. Re:Symbian is dead? by t2t10 · · Score: 1

      Most recently? E72 and 5800. They're "fine" in that basic stuff works OK; they're limited compared to modern Android phones.

    7. Re:Symbian is dead? by CAIMLAS · · Score: 1

      a) News of symbians death are IMHO highly exaggerated.

      Dollars to doughnuts, FreeBSD dies before Symbian.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    8. Re:Symbian is dead? by crwl · · Score: 1

      It's a bit unfair comparing modern Android phones to Symbian phones released in 2008 and 2009. What about the N8?

    9. Re:Symbian is dead? by t2t10 · · Score: 1

      I tried it out, it's not all that different; basically, many of the same limitations. It also was a little sluggish and text input is still tedious.

      Don't get me wrong, phones like the N8 have some things going for them: better battery life and better cameras, for example. But on balance, I think most people are better off with Android. People buy Symbian phones for the hardware, despite the software.

      MeeGo may be a more serious competitor.

  26. Re:Why would anyone want Nokia to do something awf by Bert64 · · Score: 4, Informative

    I can get a bash shell on my nexus one, and from there its possible to install a full standard gnu userland. The only difference with meego is that the standard userland is already there, but nothing stopping you from installing what you need on android.

    That said, why would you want to install ruby on a phone? I grudgingly have ruby installed on my relatively highend laptop, and it's an absolute pig, i would hate to have something so inefficient on a far less powerful device with a smaller battery.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  27. Re:Nokia isn't exploiting the right opportunities. by Bert64 · · Score: 1

    Nokia were the early adopters, symbian predates android and ios by several years. The problem is they let it stagnate and get overtaken.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  28. Please no android, give me business features .. by Anonymous Coward · · Score: 0

    Please no android, give me business features .. like an complete and open calendar API as android is completely lacking. Together with the possibility to sync with Caldav. (although you should be able to build it yourself when the calendar api is free.

  29. It gives then an edge by AHuxley · · Score: 2, Insightful

    Real Linux, copyleft license, BSD-style licenses. Not been associated with Google can be a good thing too.
    Unix is free, open and a offers a powerful community.
    Google only offers open layers down to a 'base' that maybe hardware or software.

    --
    Domestic spying is now "Benign Information Gathering"
    1. Re:It gives then an edge by Anonymous Coward · · Score: 0

      Excellent points -Interesting the the author and most of posters reflexively assume Meego is inferior and a business/political choice over Android.

      Perhaps the original poster could have considered the possibility that the reverse is true: Meego is superior in several respects and that some of Google's design decisions were more business/political (pacifying control-freak telcos) than technical.

      Intel, for one, who drove both Meego and the earlier Moblin incarnation, is all about enabling more powerful Atom processors for handsets so excellent performance and multitasking, openness (meaning broadest adoption to increase Atom market share) - basically technical superiority - IS the defining objective of Meego. Google just wants Android on as many handsets as it can get, which means dumbing it down to the lowest common denominators ( has to run asap on the least capable ARM processors possible) to get max number of eyeballs for the eventual ad platform Android handsets will become.

      Meego handsets are still in dev until upcoming generations of Atom that have better power characteristics are available starting in 2011, but watch out then.

    2. Re:It gives then an edge by hweimer · · Score: 2, Interesting

      Plus the potential to run Android apps under MeeGo, probably even natively at some point.

      --
      OS Reviews: Free and Open Source Software
  30. TFA is FUD, Symbian not dead. by ThoughtMonster · · Score: 4, Insightful

    Seriously, any posting on Nokia/Symbian/MeeGo will have the inevidable person calling Nokia to adopt Android but this one gets the cake, claiming that "Symbian's dead, and MeeGo won't cure ailing Nokia". Nokia's recent press release (Engadet coverage) claims the exact opposite, e.g. that Symbian and MeeGo are gaining unified development environments via Qt and Symbian is now a consolidated effort, unifying the seperate Symbian ^x releases into a constantly evolving release model (which means that older phone models will get constant feature improvements instead of just bug fixes). Nokia had a good Q3 and last I checked, they still held the majority of the mobile phone market. Talk about missing the point.

    Why are we giving these people creedence again? Oh yeah, he writes for InfoWorld, that must mean he's on to something.

    1. Re:TFA is FUD, Symbian not dead. by Anonymous Coward · · Score: 0

      Where I come from a company is considered "relevant" if they have the biggest freaking market share (bigger than the combined share of the next 3 largest companies).

    2. Re:TFA is FUD, Symbian not dead. by Fnord666 · · Score: 1

      Oh yeah, he writes for InfoWorld, that must mean he's on something.

      There, fixed that for ya.

      --
      'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
  31. Symbian is not being scrapped. by Anonymous Coward · · Score: 4, Insightful

    Nokia is not closing down Symbian, it looks like it might close down the Symbian Foundation (http://www.allaboutsymbian.com/news/item/12215_Nokia_accelerates_Qt_focus_con.php)

    The new CEO, mr Elop, has stated that Qt will be the main API for both Symbian and MeeGo, and that the two different Qt-based UI's for Symbian and MeeGo are either scrapped (Orbit on Symbian) or deprecated (DirectUI on MeeGo). Also, evolution of Symbian will proceed more smoothly so the numbering system (^3, ^4) is dropped.

    Finally, it looks like people can upgrade their devices to later versions of the OS.

    In a couple of weeks is the Symbian Smartphone Show or whatever it is called now (http://www.see2010.org/).

  32. I like Yellow by bananaendian · · Score: 2, Insightful

    I'm writing this on my MacBook Pro, my other work machines are Windows PC's. I administer a UNIX server at the laboratory. I do most of my work on LabView and AutoCAD. I edit my photos with Photoshop and I drive my Ford to the local supermarket at the mall and buy the biggest brand cereal. And in the evening I sooth myself with a bottle of JD.

    I use stuff so I can be productive and happy. I dislike smug people who announce their dislike of stuff so they can feel superior to me. They're not. They are just voicing their own failure at being happy.

    Oh, and TFA: Nokia should stick with Meeguu - its the only chance they have in the face of technically superior handsets from HTC and superior user experience/cool-factor from Apple. Otherwise they're just a redundant manufacturer of slightly better quality handsets that cost more and don't look cool. A virtual death sentence in the mobile market. As for /. ... nobody gives a thing what you think - the mobile market is even more brainless-consumer oriented then Apple's if you know what I mean.

    --
    www.tribalnetworks.org - helping tribal people around the world to own their own means of high-tech communications
    1. Re:I like Yellow by Anonymous Coward · · Score: 0

      Ignorance is bliss. Life is tragic for the more intelligent.

    2. Re:I like Yellow by anshulajain · · Score: 3, Insightful

      I'm writing this on my Ubuntu laptop (corporate), my work systems are all Linux (Ubuntu, Mandriva) and I administer a large number of Linux systems deployed for mission-critical manufacturing test...oh my work is all on LabVIEW, besides using Linux for all "other" corporate work (I'm among the senior management at work)

      I edit my pics with Shotwell and Picasa and drive the latest Honda to the local supermarket. I like to relax in the evening with some nice music and enjoy time with my family.

      I use Linux to be productive and be happy. I dislike smug people who think that Linux users have little or no life. They're just trying to act intellectually superior compared to others.

    3. Re:I like Yellow by Crayon+Kid · · Score: 1

      I dislike smug people who announce their dislike of stuff so they can feel superior to me.

      Who said GP was trying to feel superior to you? He just said it's possible to dislike software. Talk about being self-centered.

      And in the evening I pleasure myself with a bottle of JD.

      Fixed.

      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    4. Re:I like Yellow by Americano · · Score: 1

      Interesting how your post focuses on the things you like, rather than a list of "everything I don't like," huh? You just made gp's point for him - use what makes you productive and happy - best tool for the job, based on your own preferences, and stop spending time whining about all the stuff you don't like.

    5. Re:I like Yellow by eugene2k · · Score: 1

      I like people who understand that no one cares what they like or dislike.

      --
      Apple has "Mac vs PC", Microsoft has "Laptop Hunters", Linux has recession
    6. Re:I like Yellow by Anonymous Coward · · Score: 0

      If you drink JD and call yourself happy, you have terribly low standards :-(

      I would feel sorry for you, but from your post I'm not sure you'd appreciate that.

    7. Re:I like Yellow by Anonymous Coward · · Score: 0

      I dislike smug people who announce their dislike of stuff so they can feel superior to me.

      That goes really well with this tidbit:

      the mobile market is even more brainless-consumer oriented then Apple's if you know what I mean.

    8. Re:I like Yellow by Anonymous Coward · · Score: 0

      I dislike smug people who announce their dislike of stuff so they can feel superior to me.

      The story title asked a question. The GP suggested a possible answer. No "feeling superior" involved.

  33. Product Differentiation, anyone? by tsj5j · · Score: 1

    I thought the answer was blatantly obvious: product differentiation. Nokia and their high costs in both location and labour will never be able to compete at a cost-level with companies like HTC who can push out android phones faster and cheaper than European companies. If they lose their only differentiating factor (software), they're reduced to little more than a hardware-assembling company.

    1. Re:Product Differentiation, anyone? by puto · · Score: 1

      Nokia produces tons of phones in china, they have a huge operation there.

      --
      The Revolution Will Not Be Televised
  34. Come on Nokia by JamesP · · Score: 1

    I really want to know who messed this up...

    They have an alternative to Symbian, it's called Maemo
    Someone came up with this MeeGo thing, which is great, but it shouldn't be against Maemo

    They have a cell phone with Maemo, the N900

    The should begin getting Maemo to run on other platforms (maybe even the X8 one) and instantly fire anyone who starts whining about it

    --
    how long until /. fixes commenting on Chrome?
  35. yeah, right... by Kludge · · Score: 4, Interesting

    Porting a python run time would be a pain in the butt. And even if it worked what libraries would it have?

    I wrote a python script on my laptop that grabs some data off the network and displays it in a GTK window for the user. I then copied that program to my N900 and it just worked. Try that on your Droid.

    1. Re:yeah, right... by Anonymous Coward · · Score: 1, Informative

      Porting a python run time would be a pain in the butt. And even if it worked what libraries would it have?

      I wrote a python script on my laptop that grabs some data off the network and displays it in a GTK window for the user. I then copied that program to my N900 and it just worked. Try that on your Droid.

      There already is a Python runtime for Android. Has been for a year and a half.

      http://google-opensource.blogspot.com/2009/06/introducing-android-scripting.html

    2. Re:yeah, right... by Anonymous Coward · · Score: 0

      On the other hand, the Python runtime has a very limited set of libraries compared to a full-fledged Python installation on Windows or a N900, and you can't easily add new ones that depend on external native code. In other words, most of the libraries that make Python so useful are right out.

  36. From Maemo to DeadGo by xnpu · · Score: 1

    Maemo was great. I loved Maemo. Debian based, about to get the love of Nokia's QT team, etc. It had a lot going for it. Just that Nokia should have slapped a capacitive touchscreen on the N900 and whip up a decent Twitter client.

    Meego will be a disaster, for the simple reason that Intel is involved. Instead of betting on the QT team that Nokia acquired, which knows it's stuff, they're betting on a company which have never ever come up with a piece of good software. Nokia's management of the last 1--2 years is really brain-dead IMHO.

    Swapped my N900 for Nexus One. Smooth phone, but boy do I miss the N900's Skype and integration. Nothing beats a video call with grandma on the other side of the globe over 3G!

  37. The troubles of big corporate. by Anonymous Coward · · Score: 1, Interesting

    Nokia suffers, no more no less, the same trouble of a big Corporate grown up too fast in a country where that business model was previously, simply enough, not present.

    What comes out is an organization model that, put in a linear way, does not understand the world around its core business. Think of M$.

    There are certainly clever individual minds in the business and clever ideas that changed the world, but that creativity must be so stifled by corporate shit to be unable to come to the surface anymore.

    Insisting with such an old style monolith like Symbian; delaying touch screens up to almost stubbornly negating their existence; letting camera and video functions and technology lag behind of the concurrence: it came to a point that both hardware and software on Nokia phones now lag behind every other big on the market, from Apple to Samsung, to Google and so on. There is enough to wonder how does Nokia still survive.

    Nokia survives through all the customers around the world, also in less developed not-western countries, who simply need one thing: make phone calls and now and then sending an SMS.

    But Nokia ought to be warned, or maybe has already miraculously realized it: that won't last for long. Even POTS operator at one time had to accept they had to differentiate on the Net as platform, that their beloved phone line could not sustain them forever.

    Will the new chief go along and get through those troubles? It depends how bureaucratized the thing has become.

    Certainly going to this MeeGo, if confirmed, that would mean: jumping off the market completely, leaving Symbian at once, letting bleeding edge Android on a side and thus giving huge advantage to Apple: it looks at first sight as a not-very-clever way to start. Some would call it visionary,instead. Will Nokia recover or bust? We'll see over a few years.

  38. Re:Why would anyone want Nokia to do something awf by Anonymous Coward · · Score: 0

    I can get a DOsH Prompt on my phone ... every-time it runs out of credit ...

    All your opinions here amount to less than a Camels fart, the Market will decide, and they don't read, this.

  39. MeeGo choice by kathycat · · Score: 1

    If you think Nokia's position, choosing Android or WP7 will lead Nokia to be only hardware manufacturer where price is main competitive issue. That will lead price erosion, dropping profits per device, Exactly opposite than Apple's case. That would mean that Nokia will give up ever make good profits or compete with Apple any more. I am about sure that making standard WP7 or Android, profit per device won't be even 1/10 that Apple gets. That means that even selling 10 times more devices than Apple, Nokia would not make same amount of money and it is difficult sell 10 times more when there is dozens of competitors with similar devices with similar price in market. Based on Gartner Windows Mobile has lost 1Q09 10.2% to 1Q10 6.8% compared Symbian 48.8% to 44.3% . Most stupid choice would be switching loosing standard platform where you are just HW manufacturer of losing platform. Thing that Nokia needs is platform that is clearly best on market and that MeeGo clearly is and it needs platform where Nokia can differentiate from competitors, not be just HW manufacturers. Why I think that MeeGo is best ? It is based on standard Linux environment, not just dalvik and Java top of Linux kernel. For application development Qt and Qt Quick ( Qml and Qml components ) has lot of great innovations and Qt has already large OSS community and a lot of commercial users. Is user view, if you go and look MeeGo UI demo videos, it is one that can compete against Android and iOS.

  40. risky by t2t10 · · Score: 1

    Financially, I think it's obvious that the best strategy for Nokia would be to ship Android and go to town developing Nokia-specific add-ons for Android. A good Android implementation plus Nokia software would instantly give them back the smartphone market.

    For the market as a whole, I'm glad they are taking the risk with MeeGo. I would like to see a native Linux smartphone platform: it's easier to port software to, and Nokia may have enough clout to make it stick. In some sense, MeeGo is much closer to iOS than Android: like iOS, MeeGo uses older programming technologies based on native code.

  41. never say never by luis_a_espinal · · Score: 2, Interesting

    Android is all cool and stuff, it's also FLOSS and great, and whatever.

    However, it has its shortcomings which make it less than a desirable phone operating system for me. First of all, MeeGo, Maemo and their cousins allow me to run any vanilla GNU/Linux GUI applications. They are most often inconvenient to use on a phone, but they are sometimes better than what's available on the platform. On Android I'm limited to apps written for Android. Thanks but no thanks.

    Also, programming for Android? You need Java or another language that compiles for JVM.

    Just a small (but very important) correction It's not the JVM, but the Dalvik VM. Bytecode is different, architecture is different, and Dalvik by design will not run J2ME things that can run on a JVM.

    Want to program in Python? Good luck. You can't, and you'll never can, because Jython isn't portable to Android.

    Considering that Google App's engine primary language (for a while) was Python, I doubt that Python (or a subset of it) will never be supported on Android. To run Python on a VM, you. do. not. necessarily. need. Jython. You simply need (a yet to be developed) Jython-like equivalent for the Dalvik.

    Obviously you would not get all the amenities you'll have on Python (.ie. ability to call C libraries.), but then again, you do not get all the Java amenities on Dalvik anyways. Now, the status quo is all the result of strategic considerations.

    Google App engine supports Python and Ruby (and even Scala IIRC) because the web development bestiary is that much diverse. It caters to the widest possible set of development shops, a good strategic move.

    Dalvik on the other hand started (and has remained so) with support to a subset of Java. Why? Because it caters to the masses of J2ME developers already in existence; another strategic move, and a better response to iPhone's reliance on Objective-C.

    The Oracle-Google legal wrangling might actually give Google a reason to start supporting a different programming model should it comes to that. Given its historical support for Python, it could come to that as it is not infeasible (given Google's engineering resources), nor foreign (given its history with Python.)

    There is nothing technical that prevents a subset of Python from ever running on Dalvik, ergo my objection to your position, which I quote - "You can't, and you'll never can, because Jython isn't portable to Android"

    Want to program Ruby? Haha. With non-Android distros I can write an app, run it on my desktop without any additional software installed, and then copy it to the phone as is. And it will run.

    Again, nothing prevents this from occurring. More power to you if you can write Ruby apps on non-Android distros, but you seem to be missing the point about the nature of Android and the mobile development marketplace. It locks on a Java variant because it is strategically sound to lock and focus on the masses of J2ME developers (not on virtually non-existing mobile python/ruby masses.)

    More importantly And there is nothing on Dalvik that prevents it from EVER and FOREVER running something else should market forces end up driving that need.

    1. Re:never say never by gbjbaanb · · Score: 1

      Dalvik on the other hand started (and has remained so) with support to a subset of Java. Why? Because it caters to the masses of J2ME developers already in existence; another strategic move, and a better response to iPhone's reliance on Objective-C.

      This confuses me, see if they wanted a strategic language for Android that gained a absolute heap of developers, J2ME wasn't it. It was C/C++ as used by Symbian. Add some symbian->Android conversion tools, libraries or frameworks and you'd have had a massive amount of development loveliness. To point this out, on many Android forums one cry I used to read a lot was "how can I port my existing C++ code to Android, why did they make it all Java".

      I think Google went Java because it was their 2nd (or is it 1st) choice language, and the guys doing the phone API happened to want to make it Java, probably no other reason than that. Now they should start improving the Qt abilities and getting a richer software ecosystem going instead of trying to lock it all down to Dalvik-code only. (ie make it easier and more supported, to write in C/C++ and maybe Python too)

    2. Re:never say never by shutdown+-p+now · · Score: 1

      This confuses me, see if they wanted a strategic language for Android that gained a absolute heap of developers, J2ME wasn't it. It was C/C++ as used by Symbian.

      They likely wanted a memory-safe, easily sandboxed language.

    3. Re:never say never by shutdown+-p+now · · Score: 1

      Obviously you would not get all the amenities you'll have on Python (.ie. ability to call C libraries.)

      Why not, since Dalvik implements JNI?

    4. Re:never say never by luis_a_espinal · · Score: 1

      Obviously you would not get all the amenities you'll have on Python (.ie. ability to call C libraries.)

      Why not, since Dalvik implements JNI?

      Possibly because of the same restrictions placed already by Dalvik on the type of libraries one can execute under the java.* and javax.* namespaces.

      I mean, this is all speculation from my part, but if Dalvik - by design - restricts on what is available under the java/javax namespaces (for a variety of reasons), it will also follow that it will put restrictions on executing arbitrary native code via JNI (as Google App Engine does now.)

    5. Re:never say never by shutdown+-p+now · · Score: 1

      Possibly because of the same restrictions placed already by Dalvik on the type of libraries one can execute under the java.* and javax.* namespaces.

      I'm not sure what you mean by this. Android does not provide the complete set of J2SE class libraries, but that's not a restriction, it's just a lack of a feature. You can write your own and use them, and it won't stop you.

      I mean, this is all speculation from my part, but if Dalvik - by design - restricts on what is available under the java/javax namespaces (for a variety of reasons), it will also follow that it will put restrictions on executing arbitrary native code via JNI (as Google App Engine does now.)

      No need to speculate. Android does support JNI, and it does allow arbitrary native code execution.

  42. Re:Why would anyone want Nokia to do something awf by lee1026 · · Score: 1
  43. command line tools by G3ckoG33k · · Score: 1

    "My first question is; how many people will be running command line tools on their phone?"

    Count me in, cowboy! That is one! :)

    "Second the code must run on an ARM so must be written for an ARM. Can I easily port my Android or iOS app to MeeGoo? I doubt that very much."

    But, we can't count on you?!

  44. Maemo? by Veroxii · · Score: 1

    What on earth happened to Maemo? It's running on my N900 right now and pretty awesome. Who wouldn't like some debian niceness on their phone?

  45. Wtf is this shit? by aliquis · · Score: 1

    "ending the Symbian 3 and Symbian 4 efforts"

    Source? Two days ago they said they would keep developing Symbian but not talk about Symbian^3 and Symbian^4 but rather one steady process and release the changes to the phones as soon as they was available instead.

    Also why wouldn't they release MeeGo?

    And sure they could pick Android any day, or Windows Mobile 7, but it's not like either would be better than MeeGo.

    Pure bullshit 100%?

  46. I "think" they are doing that by floydman · · Score: 1

    I have been contacted by a "confidential" Finnish company requesting QT developers with Meego experience. I have not read the FA, just the title.

    I have the Qt experience, but not the Meego, I just though this could be relevant.

    --
    The lunatic is in my head
  47. Meego cert for in-flight? by Anonymous Coward · · Score: 1, Interesting

    Well, meego is based on VxWorks, and VxWorks in certified to DO-178B level A, and level "A" cert specifies that any failure may result in loss of aircraft or injuries. I see this as a A-OK for cell phone use during flight.

    1. Re:Meego cert for in-flight? by Eunuchswear · · Score: 1

      Mods on crack.

      No, dummies, MeeGo is not based on VxWorks. It's Linux.

      --
      Watch this Heartland Institute video
  48. I hope Nokia comes up with something good by jonwil · · Score: 1

    Give me a phone with hardware at least as good as the N900 (including the physical keyboard) and an OS that is as hackable as Maemo on the N900 is (i.e. nothing at all to prevent you replacing any and all parts of the firmware, 100% open kernel etc) and it will be my next phone (assuming Android vendors like HTC and Motorola dont start becoming more open in the meantime and assuming a 3G version of OpenMoko doesn't appear)

    Bonus points if it includes Nokia Maps Navigation for Australia like other Nokias have.

    Right now, the only "hackable" phone I know of with a physical keyboard is the N900 and the software stack on that phone doesn't seem to have a future (even less so if MeeGo is DOA or never appears)

    The OpenMoko Freerunner has no physical keyboard and a cellular radio that's worse than what one finds is most entry-level phones from the big names.

    The Nexus One has no physical keyboard and I am not 100% on how open the software stack is.

    The HTC DeeZire Z has a physical keyboard but the software stack is locked down tight.

    1. Re:I hope Nokia comes up with something good by Anonymous Coward · · Score: 0

      Right now, the only "hackable" phone I know of with a physical keyboard is the N900 and the software stack on that phone doesn't seem to have a future

      FYI PR 1.3 for the N900 is coming soon, and it will allow dual-booting Meego as well.

  49. MeeGo FTW by paxcoder · · Score: 1

    Who is Ted Samson, and what is his problem with MeeGo?

  50. Re:Why would anyone want Nokia to do something awf by Bill_the_Engineer · · Score: 1

    All things are technically possible with software, the question becomes would the reward justify the effort. The parent was referring to the fact that he could run his programs on Maemo with very little effort. You can't say that is the case with Android.

    --
    These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
  51. Some think Symbian will be around a while... by ibsteve2u · · Score: 2, Informative
    Some think Symbian will be around a while...

    There are two reasons why Nokia won’t be abandoning Symbian anytime soon.

    Firstly, Symbian is tightly integrated with Nokia’s variant management process. Nokia is the only OEM that has mastered variant management, i.e. being able to generate 100s of variants (SKUs) at the press of a button. That’s how Nokia can deliver 100s of customised smartphones to operators and retailers around the world. This variant management process is ‘hardcoded’ to Symbian, which means that replacing Symbian would seriously compromise Nokia’s ability to cater to operator requirements around the world and it would seriously hurt its market share.

    Secondly, Nokia’s economies of scale rely on in-house control of core components, and the operating systems is one of them. If Nokia were to license Windows Phone it would reduce its differentiation to industrial design and Ovi alone. In the case of Android, Nokia would have to branch Android (and to sustain the cost of Android development), port Qt on Android which means another 12+ months for a stable implementation. While this remains a long-term possibility, it is still a gamble when Nokia’s priority should be to focus on killer devices and not a killer OS. Qualcomm’s BREW MP is another candidate but only when Qualcomm has a good developer platform story and that means waiting for BREW MP to launch a web-based platform akin to RIM’s WebWorks.

    Symbian may no longer be a symbiotic system, but will live within Nokia for many years to come as the workhorse under the hood of Nokia smartphones.

    --
    Orwell: "In a Time of Universal Deceit, telling the Truth is a Revolutionary Act"
  52. Too late for developers... by lxt · · Score: 2, Interesting

    It seems that Nokia has a bit of a following on /., probably because their hardware is pretty decent, and key handsets like the N900 appeal to the demographic here. But the fact is in terms of an *ecosystem*, Nokia has nothing. They are in the gutter.
    Nokia are at the point where they are actively having to pay developers to write apps. And we're not talking small apps here - big, branded apps for global companies, who are being approached by Nokia asking them if they'd like an app for Ovi. I couldn't tell you the number of clients I deal with day in day out during my day job who have already been rung up by Nokia. Even with an app developed at no cost, very few companies will take Nokia up on it.
    It is simply not a space that people want to release software into right now. It doesn't get you press, and it doesn't get you sales. At least Blackberry have realised their previous app space strategy wasn't working, and are attempting to engage with mobile developers in a meaningful way. Nokia's left there without a clue.

    1. Re:Too late for developers... by Anonymous Coward · · Score: 0

      Considering Symbian has pretty much a majority market share, this sounds very unlikely....

    2. Re:Too late for developers... by NuShrike · · Score: 1

      Don't forget Qt begging on Twitter for examples of mobile Qt apps.

      Summary is Nokia/Qt is Beta SP. It doesn't matter it's better tech if the majority doesn't buy into it.

  53. Re:Why would anyone want Nokia to do something awf by Bill_the_Engineer · · Score: 1

    The only difference with meego is that the standard userland is already there, but nothing stopping you from installing what you need on android.

    Well except the restricted memory space and you still need to load a libraries to support the standard userland. The N900 was built with the intention of running Maemo. The Android OS was made to run on resource limited devices such as the nexus one. I'm not saying it's not possible to run a standard GUI on the nexus one, I seen linux GUI run on less (like my ancient Sharp Zaurus). I just have my doubts that the standard userland can run within Android and actually be useful (speed may be a concern).

    Of course the phones will get more powerful, and soon the hardware will support running Linux programs alongside Android. This will be feature supplied by the hardware and made possible by the linux kernel that Android runs on top off. Not exactly Android itself.

    --
    These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
  54. Re:Why would anyone want Nokia to do something awf by grumling · · Score: 2

    You CAN GET a bash prompt on your Nexus 1. While Maemo COMES WITH a CLI out of the box.

    "Rooting" the phone was as simple as enabling the extras repo and getting the gainroot application (which I believe comes from Nokia).

    Then open the CLI, type sudo gainroot and watch as the prompt changes to a #.

    Done. No screwing around with custom kernels, waiting for the "community" to figure it out, etc.

    But the reality is that mobile phones aren't built for people who care about such things. If Nokia survives the handset wars, it will be in a role kind of like HP calculators: everyone else uses TI, so when you try to explain how easy it is to do complex math using RPN, they don't get it.

    --
    "Well, good luck finding a judge that doesn't run a bestiality site."
  55. Easy... Profit by __aazsst3756 · · Score: 1

    While android may own the market, the companies with their own OS are making the majority of the profit. Shipping android is the equivalent of yet another beige box computer maker, it is a race to the bottom profit wise.

    Asymco Profit Analysis

  56. Did you forget Microsoft? by Anonymous Coward · · Score: 0

    I just don't understand how people forget where the new CEO is coming from. Microsoft. Stephan Elop lead one the cash cow division of Microsoft. He did a great job overthere even with some unsuccessful project. However those doomed projects like project green build up some of the greatest technology assets that Microsoft is leveraging now. The core of the Windows Phone team is coming from those higly innovative projects. Stephan may become a close ally of Microsoft providing special Nokia content.

    And I agree. The lower segments of the phone industry they will still build on theid own platform.

  57. Brand loyalty by Compaqt · · Score: 1

    I think the reason it counts is that all those hundreds of millions of people with "dumb" Nokias will look first at Nokia for their first smartphone purchase.

    People are creatures of habit, and just as it's tough to get Windows users to switch to Linux, and iPhone users to Android, I think Nokia users are going to stick with what's familiar. I've tried Sony-Ericson, and it was horrible (for me).

    The decline in Nokias share is due to other manufacturers coming in the market; otherwise Nokia's sales are up 61%.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  58. "or even Windows Phone 7"... by gmuslera · · Score: 1

    ... are you serious? Yes, in a future it could eventually get cut and paste, while keeping iOS 2 style "multitasking". One thing that have Maemo over iOS and even Android is multitasking, you can run a lot of tasks, easily switch between them, and all running (as far the cpu holds, of course). WP7 have a broken design in that area. And betting that your users "won't need multitasking" is pretty close to say that they don't need a smartphone neither.

  59. Just switched to an N8, from an N82. by Rexdude · · Score: 3, Interesting
    It's quite a solid piece of hardware, and Symbian^3 isn't bad either. The first firmware update later this year promises to update the built in Qt runtime to 4.7, replace the existing dog of a S60 browser with a Qt based one, and other improvements.
    And because of the way Symbian's been designed from the ground up to work with limited CPU cycles/memory, it runs exceedingly well with a 680 MHz ARM11 and a Broadcom GPU. Angry Birds has been ported to Symbian, Need for Speed Shift looks gorgeous, and HD videos play smoothly on the AMOLED display. Detractors crow over the gigahertz class CPUs on rival Android/iOS devices, but consider that Android practically REQUIRES that sort of CPU power for its eyecandy. A lower specced Android phone just doesn't cut it for speed. And while battery technology doesn't keep up with clock speed, GHz level CPUs are going to guzzle battery as well.
    My phone lasts great for 2 days with wifi permanently on and push email running for GMail/Hotmail/Yahoo, with around 2-3 hours of calls a day and moderate web browsing and youtube. It has a power saving mode as well, that reduces display brightness and other settings in one go to consume less power.

    For all the bullshit in this article, he never even talks about Nokia's Q3 financial performance. They've sold 26.5 million smartphones, with an operating profit of €529 million, and net sales of €10.3 billion. Today in India, you can buy a Symbian based Nokia C5 for about INR 7000 unsubsidized (about $160). Just a couple of years ago that was unthinkable for a Symbian phone, they typically cost double or more. Nokia's pushing smartphones lower into the mass market with Symbian - they're able to standardize the hardware (600 MHz ARM CPUs as of now) and because of Symbian's scalability it can power these low end handsets. Meego will wind up for the successors to the N900 and probably be a netbook/smartphone hybrid OS, with appropriately beefy hardware and targeted at the high end market. And both Meego and Symbian will be bound by Qt for application development, so that there's no fragmentation going forward for developers. Qt is a proven toolkit, in use by Skype, Google Maps and VLC, and can be used to make desktop apps for Windows/Linux/Mac as well. And naturally everything here is true honest open source, not locked down or restricted like the 2 competing phone OSes(Android the OS being restricted by its device manufacturers even if it itself is open source). I see this as quite good - an incentive for developers to write apps that will reach the entire world, not just the US (there's 10 million downloads a day on Ovi Store as of now, it seems), while using standard development tools that can be used outside of mobile phones as well.

    --
    "..One hosts to look them up, one DNS to find them, and in the darkness BIND them."
  60. MeeGo: Actually a Linux by LordMyren · · Score: 1

    MeeGo is a Linux. That largely defines MeeGo and sets it apart. Oh sure, Android and countless other consumer electronics systems have Linux, but that distinction is relegated to some machinery under the hood kept far far away from users and often developers. MeeGo, on the other hand, is a Linux distribution, one with an integrated desktop environment that defines the distro, but it is still 'merely' a distro. It runs X. "Linux programs" will run on it.

    Android threw out Linux. Nokia hopefully isnt dumb enough to hop on that bandwagon. Isnt dumb enough to turn over the fate of their company to an OS where they'll be able to have only the most meager means of distinguishing themselves, where distinguishing yourself will earn you animosity for fracturing the local ecosystem, where Nokia's existing code base will be useless.

    Nokia can leverage huge code bases like GStreamer to get video conferencing, hardware supported media playing, to build DLNA systems on top of. You want that 21st century network functionality on Android? Have run rebuilding it chums. It's the same story, up and down, Android's core platform is tiny whereas the amount of Linux code out there to build off of is colossal.

    Last, remember who bought Qt, and consider then that MeeGo is based on Qt.

    MeeGo is a consumer Linux. That puts it in an elite realm with only one peer: Maemo. For this to become epic, only one thing is needed, UX. Everything non-technical must be done well. Even at these early stages, the netbook profile certainly is incredibly slick and integrated, hopefully the mobile profile will be similarly cared for.

  61. Re:Why would anyone want Nokia to do something awf by metamatic · · Score: 2, Informative

    Also, programming for Android? You need Java or another language that compiles for JVM. Want to program in Python? Good luck. You can't, and you'll never can, because Jython isn't portable to Android. Want to program Ruby? Haha.

    SL4A for Android from Google gives you Python and Ruby right on your Android phone. Also Perl, Lua, JavaScript, Tcl and shell. In other words, you're about as wrong as it's possible to be.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  62. Short answer... by roc97007 · · Score: 1

    Because competition is good.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  63. Re:Why would anyone want Nokia to do something awf by shutdown+-p+now · · Score: 1

    First of all, MeeGo, Maemo and their cousins allow me to run any vanilla GNU/Linux GUI applications. They are most often inconvenient to use on a phone, but they are sometimes better than what's available on the platform.

    That just goes to show that "what's available for the platform" isn't much. Which is an argument against Maemo/MeeGo, if anything.

    On Android I'm limited to apps written for Android. Thanks but no thanks.

    Yes, but there are plenty of apps written for Android. It's pretty hard to find something for which there isn't an app these days.

    In contrast, when we look at e.g. N900 - if I go to Nokia app store, restrict listing to N900 only (by default it also shows stuff for S60), and browse through the list of all apps, there's a grand total of 80. Yeah, I see why you'd need to run those vanilla Gtk apps on that now... with all the pain of dealing with UI not designed for touch...

  64. Re:Why would anyone want Nokia to do something awf by Bert64 · · Score: 1

    Actually, the nexus one is considerably more powerful than the earlier maemo based devices like the n700 and n800 tablets.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  65. Re:Why would anyone want Nokia to do something awf by shutdown+-p+now · · Score: 1

    "Rooting" the phone was as simple as enabling the extras repo and getting the gainroot application (which I believe comes from Nokia).

    Then open the CLI, type sudo gainroot and watch as the prompt changes to a #.

    Done. No screwing around with custom kernels, waiting for the "community" to figure it out, etc.

    You don't need to screw with custom kernels on Android either, if you get the right phone. The procedure for rooting Nexus One is officially documented, and does not require any side downloads or custom kernels.

  66. MeeGo by codepunk · · Score: 1

    I feel they are on the right track and should stay the course. Android is completely hobbled by running a jvm instead of native code. It is the reason you do not see crap for
    games on the android since the stack is not efficient enough. MeeGo on the other hand runs native code, porting stuff like iphone games which push the device processing limits
    will be a real possibility.

    --


    Got Code?
  67. Not reading the same info I'm reading by CAIMLAS · · Score: 1

    In September, Symbian 3 was Nokia's latest great hope for becoming relevant in the modern smartphone market.

    Are we paying attention to the same market? Symbian hasn't been relevant for a long time for smartphone use; they've been feature phones, as far as I'm concerned, and not terribly good ones at that.

    As for MeeGo... why? I can understand the motivation behind it, but not why they're essentially throwing out Maemo to do so. Maemo was (is) already a long way to being mature, and Meego looks like a complete start from scratch. (Architecturally, it's also better - being based on deb packages instead of RPMs). I don't know if it's Intel stalling or Nokia, but Meego just isn't going anywhere fast enough for those interested. ("Soon enough to matter" isn't significant; a new market player with well-designed utility and good marketing will always have room to play.)

    I'm quite disappointed in Nokia in this regard. They had a lot of potential when the N900 came out - and then they fell flat on their face. Nokia, with all their different execs leaving and various other product turmoil, looks like it's starting to flounder - and will soon be failing unless they pull their ship together from the top.

    Windows Phone 7? Don't even go there. It's the same ball of suck that the iPhone is with regards to privacy and control, with none of the benefits. (Android isn't much better due to vendors locking the phones.)

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    1. Re:Not reading the same info I'm reading by 21mhz · · Score: 1

      (Architecturally, it's also better - being based on deb packages instead of RPMs).

      I keep hearing this, and I can't see why. I have maintained some Maemo .deb packages for a few years, and before that, quite a few RPM packages for another Linux distribution. I don't really see how one of the package managers is clearly better than the other.

      --
      My exception safety is -fno-exceptions.
    2. Re:Not reading the same info I'm reading by CAIMLAS · · Score: 1

      Part of the problem is in how RPM allows requirements to be met; it can lead to quite a few different "can not install this package, can't install requirements as it conflicts with something else". In contrast, DEB has "x requires y" - it's not as open-ended, and trying to deviate from it is at-your-own-risk.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    3. Re:Not reading the same info I'm reading by Compaqt · · Score: 1

      >Are we paying attention to the same market? Symbian hasn't been relevant for a long time for smartphone use; they've been feature phones, as far as I'm concerned, and not terribly good ones at that.

      Umm, what? Symbian constitutes 41% of the smartphone market, the single largest share. The next smaller share is RIM at 18%.

      http://en.wikipedia.org/wiki/Smartphone

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    4. Re:Not reading the same info I'm reading by 21mhz · · Score: 1

      Really? I thought the difference between Requires and PreReq is only in the installation order.
      Other dependency types, like Obsoletes, Conflicts, and so on, have their .deb equivalents. Actually, the existence of apt-rpm proves that there is no principal difference between the two packaging systems; apt works exactly the same way on top of both.

      --
      My exception safety is -fno-exceptions.
  68. Interesting, but... by luis_a_espinal · · Score: 1

    Dalvik on the other hand started (and has remained so) with support to a subset of Java. Why? Because it caters to the masses of J2ME developers already in existence; another strategic move, and a better response to iPhone's reliance on Objective-C.

    This confuses me, see if they wanted a strategic language for Android that gained a absolute heap of developers, J2ME wasn't it.

    Why not? The number of former J2ME developers is decent, and the transition to developing on a mobile platform is that much more cost-effective for the masses of J2SE/JEE developers out there. Google simply said "here, you know Java? Then you can use your skills almost without changes and be productive almost immediately".

    It was C/C++ as used by Symbian.

    Why would C/C++ be a better strategic language for Android? Do we have any ratio of C/C++ developers with Symbian experienced over the number of J2ME developers (and the potential J2SE/JEE developers that could be trigger happy and more than ready to do mobile stuff)?

    Also, consider that it's not the quasi-Java language that Android programmers use that is the platform. It's the Dalvik VM. It is not beyond the realm of possibilities that the same VM will support subsets of Ruby and Python for mobile development, benefiting from a core of "blessed" libraries, sandboxed on a VM (which is more appropriate for application programming).

    Add some symbian->Android conversion tools, libraries or frameworks and you'd have had a massive amount of development loveliness. To point this out, on many Android forums one cry I used to read a lot was "how can I port my existing C++ code to Android, why did they make it all Java".

    One could also make the same argument with iPhone and Objective-C. There is a matter of application control that Google is pursuing here, and I have a suspicion that Google is not that kin of C and C++ given they are looking - for better or worse - for system programming language alternatives such as Go.

    I think Google went Java because it was their 2nd (or is it 1st) choice language, and the guys doing the phone API happened to want to make it Java, probably no other reason than that.

    That's all the reason they needed to be honest.

    Now they should start improving the Qt abilities and getting a richer software ecosystem going instead of trying to lock it all down to Dalvik-code only. (ie make it easier and more supported, to write in C/C++ and maybe Python too)

    I beg to differ. With a Dalvik VM, it might be a lot easier to create a Jython or JRuby subset to run on a common managed application core than to write it down on C/C++ and having a separate Python environment (the later with code managed independently of Dalvik and the former not being managed at all). With a VM, you can establish a lot of different application policies common to all run-times, enforced at run-time, with the OS unencumbered by them.

    It is a model that has worked well on all flavors of Java, and on all things run by a VM (Erlang, Ruby, etc.) Google could have also gone the way you described, but I suspect they decided to go the way they did for the reasons mentioned above.

    1. Re:Interesting, but... by gbjbaanb · · Score: 1

      I think you overestimate the number of J2ME devs compared to Symbian ones. There's a lot of those. And comparing anything to Apple is disingenuous as Apple wants the lock in of a little-used language, just like MS wants lock-in with .NET.

      Still, I would not have made the UI components java-based at all, as I think Java is a lock-in language all of its own (I shudder at all that "100% pure" Java marketing), I think they should have made it more as open component, probably in C, with bindings for all languages the dev likes - so you can still code in Java if you liked, or C/C++, or python, all the time knowing you were getting a first-class support for interaction with the underlying system.

      Is Java a better thing to code against? That depends on your skill set, and before anyone says 'but we need to make it as easy as possible', if that was the case, the language used would have been Basic :)

      Don't forget the VM is the OS as far as Java is concerned. Google could easily have put that work into the Linux kernel (or the Android API layer) without needing to put a VM layer on top of it all. Its all swings and roundabouts ultimately, but I think the flexibility you lose by enforcing Dalvik is ultimately detrimental.

    2. Re:Interesting, but... by luis_a_espinal · · Score: 1

      I think you overestimate the number of J2ME devs compared to Symbian ones. There's a lot of those. And comparing anything to Apple is disingenuous as Apple wants the lock in of a little-used language, just like MS wants lock-in with .NET.

      My comparison was never meant wrt to open vs locked-in. It is a given that any of the ones mentioned are meant as a way to lock in a given share of the consumer and development market.

      Still, I would not have made the UI components java-based at all, as I think Java is a lock-in language all of its own.

      It's always been a lock-in language. Where is the surprise in that?

      (I shudder at all that "100% pure" Java marketing),

      Why shudder at it? We have been developing from small to truly colossal systems in nothing but pure Java for the last 13 years. I don't quite follow the remark.

      I think they should have made it more as open component, probably in C, with bindings for all languages the dev likes - so you can still code in Java if you liked, or C/C++, or python, all the time knowing you were getting a first-class support for interaction with the underlying system.

      That could have been a possibility.

      Is Java a better thing to code against? That depends on your skill set

      This has nothing to do with skill sets. Really. For example, I can program in Java, C and C++ and have done programming at the application and system level, on both Unix and Windows (all the way down to the dinosaurs of Motif and raw Win32 API). But for application level programming, I'm sorry, productivity is up with a managed language (and the inverse is true for systems programming and a systems programming language.)

      I can arm an application-level app (be it a UI or a back-end system) using a managed programming language a lot faster than with C or C++.) And there are things for which I'm much more productive using the later (say, having to implement a network protocol stack, flip bits or, I dunno, communicating through the serial port.)

      Productivity is not simply about skills, but about using the appropriate tool for the appropriate task. There is no silver bullet nor golden universal hammer.

      and before anyone says 'but we need to make it as easy as possible', if that was the case, the language used would have been Basic :)

      Don't see what the problem with Basic is either. There is a lot of people that write crap code in Basic, but the same can be found with Java, Delphi or C/C++. It is an excellent tool when you need to write an application that shuttles data from one point (a db) to another (a screen) and where having to deal with the details under the hoods is not carrying a particular ROI for the given task.

      I would have a problem seeing Basic being used when a lower-level language is more appropriate... and viceversa. There are no universal tools in programming.

      Don't forget the VM is the OS as far as Java is concerned.

      Exactly. That's the idea.

      Google could easily have put that work into the Linux kernel (or the Android API layer) without needing to put a VM layer on top of it all.

      And Ericson could have done the same with their telecommunications systems. Instead they implemented and deployed the Erlang VM with quite a lot of success. Having a VM opens a plethora of advantages. VMs have been explored for almost 3 decades now, with them being successful stories in the industry for last 18-15 years. Ruby, CPython, Erlang, Java, .NET CLR and so many flavors of systems written in Smalltalk, Lisp and Prolog, each a testament of how effective VMs can be.

      There are times when you embed functionality at the kernel level. At others, you abstract it out to an operating environment running on top of it (in many cases in the

    3. Re:Interesting, but... by hazydave · · Score: 1

      And of course, the other big win in Dalvik -- the code is architecture independent. The same release runs unmodified on ARM-based cellphones, x86 based netbooks and tablets, MIPS-based STBs, etc. Sure, the NDK removes this, but it's only employed when performance is critical. And sure, the security factor... you don't really want to be carrying all those Windows problems in your pocket, eh?

      --
      -Dave Haynie
  69. Stick with it, Nokia by vik · · Score: 1

    I'm a happy N900 owner. I can install real Linux apps on my phone and I don't have to root it or wait until the app store is supported in my country. I can run OpenOffice on my phone, and have no problems getting hold of codecs, VPN, VoIP clients, X apps etc. while I see Android owners waiting and waiting, or having to hack and root their machines to get unofficial versions of nagware installed etc.

    Won't pretend it's the best choice for everybody, but Nokia has it right. Real Linux on a real smartphone.

    Vik :v)

  70. Nokia's new direction by Compaqt · · Score: 1

    I'm glad to hear that Nokia "gets it", if only now rather than sooner.

    I'm rooting for Nokia because I see it as one of the "good guys":
    -Nokia historically doesn't tie you in to a particular carrier, a kind of network neutrality. Tie-ins are anathema to the geek ethos.
    -Nokia bought Qt, the framework behind KDE, and is a KDE Patron.
    -They don't try to lock you out of your own phone like Apple does. They usually have SD ports for exandability, and easily changeable batteries (even the N8 only requires opening 2 screws).
    -You can develop on Windows, Mac, Linux for Windows, Mac, Linux, and phones.

    What I'd like to see is:
    -Good marketing, not the geeky ads for the N8
    -Eye-catching UI/graphics. The icons for Meego don't seem to be gradient-filled, drop-shadowed, anti-aliased.
    -Besting the iPhone in all aspects. Don't make consumers think about it, even if that means price parity. You can have cheaper phones with 80% of the features, too.
    -Stable, catchy names for flagship products. Not "N8", "C7", etc. Have a name that consumers and non-Nokia fans can remember. Everybody knows about the iPhone, even people who can't afford it.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  71. Qt by Compaqt · · Score: 1

    > I wouldn't want to put my money into buying an applications from the Ovi store if I knew that the phone's OS could be dead by the time the next handset came out.

    Well, Nokia just announced that they're focusing exclusively on Qt as the preferred app environment going forward, and that Qt apps will run on both Symbian and Meego phones.

    So, I think the answer would be to buy/use Qt apps.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  72. As an N900 owner by npsimons · · Score: 1

    I'd have to say, well, no. Android is better than iOS and all, but it still doesn't feel quite like a fully fledged Linux to me. Windows Phone 7 isn't even an option, IMHO. Maemo, OTOH, is basically Debian for MIDs and smartphones. I'm not entirely happy that they basically dropped the Debian part of Maemo in favor of the Redhat part in MeeGo, but I'm also not fond of the idea of only writing apps in Java for Android. Especially when I have a pretty decent language selection out of the box on Maemo. Anyone know what languages, toolkits and frameworks are available on Android? Can I write and run software on Android without another computer? How about Emacs, can I get that for Android?

    I probably should start playing around with the Android SDK, and I'm fairly certain that Android will crush, first and foremost, MeeGo. But I have an N900, and Maemo works pretty darn well for me.

  73. Symbian SDK on Linux by Compaqt · · Score: 1

    Actually, that's the Qt SDK. And it's good that they're supporting Win/Lin/Mac going forward.

    But the Symbian SDK basically seems to be Windows-oriented. The S40 SDK, even though it's for Java, is actually delivered as a Windows expanding .EXE instead of a ZIP.

    Although, you'd probably want to target Qt from this point on.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  74. Qt for cross-platform dev by Compaqt · · Score: 1

    Qt is definitely the ace for Nokia. Increasingly, the MS monopoly is being weakened, both in desktops (the rise of Mac), and alternative computing devices (smartphones, tablets, etc.).

    If you want to write a program once, you'd be smart to use Qt.

    Even if you had to do another GUI for small screens, Qt will still span between iPhone, Android, and Meego. And you can leverage your existing Qt knowledge.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  75. Certificates and the new Nokia dev process by Compaqt · · Score: 1

    Nokia will now sign the cert for your app on the Ovi store.

    You don't have to be a company anymore; you can just be an individual with an app.

    Nokia will even critique your app and UI for you:

    http://www.forum.nokia.com/Develop/Development_process/

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  76. Multitasking by Compaqt · · Score: 1

    Yeah, multitasking is a strong point of Nokia.

    It's amazing how people badmouth Symbian without knowing how the latest Symbian^3 devices work. Hold down the center key (equivalent to the iPhone's single key), and you get a list of running apps with thumbnails and an X to close them. Simple, and powerful.

    Listen to music while you're browsing your photos or the web or doing something else.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  77. Re:Why would anyone want Nokia to do something awf by chrb · · Score: 1

    . The only difference with meego is that the standard userland is already there, but nothing stopping you from installing what you need on android.

    The major difference is that Android does not have Xorg. Every graphical Linux app will run on Meego. Try running a GTK or QT app on Android?

    why would you want to install ruby on a phone?

    For the same reasons that we used to install BASIC on computers running at only a few MHz. Not all applications require high performance C code.

  78. Pointless reference article, so pointless post by j-bush · · Score: 1

    The article being sited here puts Meego in a negative light without giving any basis for this claim. Nothing more than propaganda. Here's a situation where I would support shooting the messenger.

  79. Lovecraftian OS by Sir+Realist · · Score: 1

    Are you kidding me? Give up a system apparently named after a Lovecraftian Elder Race in exchange for one named after a badly designed robot? No way!

  80. Mee go ith MEEGO. by lsatenstein · · Score: 1

    There are a great many opportunites for a MEEGO then you imagine, from Netbooks to embedded systems with small footprints that are QT and linux based. The Android is but one alternative, and that does not disqualify MEEGO for the purposes it is intended (MS alternative)

    --
    Leslie Satenstein Montreal Quebec Canada