Slashdot Mirror


Nokia Confirms Symbian Is No Longer Open Source

theweatherelectric noted an article on the H. From the article "Nokia has confirmed that it has closed the source code for the Symbian smartphone operating system. It says that despite it describing its new model for Symbian smartphone operating system development as 'open and direct' the 'open' part did not refer to 'open source' but to being 'open for business'. The 'open and direct' model is designed, according to Nokia, to 'enable us to continue working with the remaining Japanese OEMs and the relatively small community of platform development collaborators we are already working with.''"

45 of 246 comments (clear)

  1. just.. wow by VAElynx · · Score: 4, Insightful

    OK stop.
    I get it.
    Some asshole said he was "open"
    but he was only open for business

    Anyone remember this lyrics segment from one of the OpenBSD release songs (a bonus track)
    It's sad that what's a joke one day becomes reality in few years

    1. Re:just.. wow by fuzzyfuzzyfungus · · Score: 3, Funny

      Damn. Beat me to it. OpenVOX.

      In this case, it's kind of hard to see Symbian's brief flirtation with openness as a major loss; but it has always interested me that the OpenBSD guys, whose work lacks the legal terms in favor of remaining open that the GPLed Linux team has, are nevertheless some of the most consistent supporters of fully-open systems outside of the core FSF people.

      It's Nokia's code, and they can do what they want; but it is rather hard to see this as anything other than the spasmodic flailing of a dying platform, rather reminiscent of the bipolar behavior Sun was exhibiting shortly before their demise(only more serious, since the odds of Symbian related techologies being installed by the end user on a phone sold as non-Symbian are basically zero, while absolute fuckloads of non-Sun servers and desktops end up running JVMs...)

    2. Re:just.. wow by Nursie · · Score: 5, Insightful

      And those some would be wrong.

      More free for the first party that gets the code, much less free for third parties that are given binaries later.

      RMS is a zealot on this, it's true. But I applaud people who release GPL code because they are giving everyone the continuing right to learn and to tinker with the fruits of their labour, not just the first party. I also applaud people that release BSD code as it is very generous, but as an end user it is frequently less useful.

      I am not free to tinker with my playstation 3, but there is BSD code in there.

    3. Re:just.. wow by _Sprocket_ · · Score: 2

      Sometimes I find the whole holier-than-though, libre software is more like the PETA of the software world -- they're much more obsessed with the ideological purity of code.

      Funny you should say that. I was just thinking how militant the BSD fans are getting these days. Every time OSS is even implied, there's some BSD fanatic / troll going on about how the GPL isn't truly open / free / etc.

      Don't get me wrong - I've got nothing against supporting one's ideology (even if I disagree with the above sentiment - and "troll" is only on the off chance some are tossing this old argument around simply to tweak the GPL camp). But if you're going to start casting stones, you might want to check the ground you're standing on before you start.

    4. Re:just.. wow by Anonymous Coward · · Score: 2, Informative

      You are still free to play with BSD code. The BSD code is never lost. You just can't tinker with the proprietary stuff Sony put in their machine.

      MS used the BSD network stack in earlier versions of windows. The BSD folks were glad they did, because it ment the large number of machines coming onto the internet would have a stable TCP/IP stack that would play well with others. The BSD TCP/IP stack was never lost fo folks who wanted the BSD source code to play with. We all still use it today.

    5. Re:just.. wow by Eskarel · · Score: 2

      You misunderstand the GPL. People who modify GPL software don't have any obligation whatsoever to return any changes or fixes the make to you. They only have an obligation to provide the source code to people who they distribute the binaries to and to not restrict those people from further distributing that source.

      If they don't give you the binaries and the people they do give the binaries to don't want to give them source to you, you're SOL.

    6. Re:just.. wow by mwvdlee · · Score: 4, Insightful

      ...which is probably what the BSD license is most appropriate for; improving interoperability between ALL types of projects both open and closed source.
      GPL pretty much forces closed source to make their own implementations of standards, which may or may not be 100% compatible. LGPL makes it a bit less difficult but BSD (and similar licenses) make it easy for every piece of software to play together nicely.

      Idealogically, GPL is like giving a gift and demanding gifts in return, BSD is like giving a gift for the simple joy of making somebody happy with a gift. Neither one is technically better than the other; it's just a matter of personal values.

      FWIW, I release code with both BSD and GPL licenses and some others (ZLib/LibPNG, MIT and closed licenses).

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    7. Re:just.. wow by Nursie · · Score: 2

      The GPL is not less free for all users of the code. It is less free for the immediate consumer of the code. It is far more free for others. The GPL guarantees those freedoms down the line, where BSD does not.

      And BTW, the original BSD code may well go away, there's no guarantee it's going to be available forever. Making the binary distributor responsible for providing access to the source is a way to work around this.

    8. Re:just.. wow by Nursie · · Score: 2

      How is it less free for third parties? Is there an inherent right to source code?

      That's a freedom granted to all future recipients of GPL software that is not granted by BSD software, yes.

      you do not (unless the license specifies it, such as GPL does) have any right - and therefor loose no freedom

      It doesn't matter if it's an "inherent" or "natural" right, and good luck defining those by the way. It doesn't have to be.

      It is an additional freedom or right of code recipients that is granted by the GPL that is not there in the BSD license. It comes directly at the price of the right of intermediate parties to use the code without opening it.

      Much like intolerance of intolerant behaviour is not evidence of a lack of tolerance in general, I don't see someone's right or freedom to deprive others of that same right or freedom to be something I consider worth protecting.

      I guess it depends on your mindset.

    9. Re:just.. wow by Nursie · · Score: 2

      GPL - you can freely use my code as long as you pass that freedom on

      BSD - you can freely use my code including denying the downstream people the same freedom.

      It's not about forcing anyone to do it your way, it's about maintaining freedom and openness.

    10. Re:just.. wow by mcvos · · Score: 2

      I don't know all the legal details, but my understanding is:

      BSD is the academic license: use however you like
      GPL is the hobbyist's license: use, but share your changes
      Apache is the business license: use however you like, but keep the attributions, license, etc.

      No idea what the exact differences between BSD and Apache are, but with BSD anyone can release the same code under a different license if they want. With Apache, I think they can't, but they can combine it easily with proprietary code (essential for many businesses) and don't have to share the source code of all their modifications.

      I know nothing about the Mozilla license.

    11. Re:just.. wow by TheRaven64 · · Score: 3, Insightful

      The original code remains free forever. Modifications to that code (i.e. extra work) may or may not be free depending on what the person doing the modifying wants to do

      Note that this is independent of the BSD Vs GPL argument. Google has a massive amount of proprietary code in their custom version of Linux, but they don't distribute it so the GPL doesn't kick in.

      Last statistics I saw, 90% of programmers were employed on in-house projects that are never intended for distribution. Assuming approximately even productivity, this means that around 90% of code that is written can incorporate GPL'd code without having to be distributed. The only difference between the BSDL and GPL in this context is that the BSDL is simple for anyone to understand, while the GPL needs running past the corporate lawyers (who probably get nervous at at least one of the clauses and reject it).

      --
      I am TheRaven on Soylent News
    12. Re:just.. wow by Bert64 · · Score: 2

      GPL restricts some freedoms in exchange for guaranteeing others...

      Society does the same thing, for instance there are laws against murder so that people can go about their business feeling relatively safe.

      Under an anarchistic society you would still be free to go about your business, but you'd be less likely to without an armed guard.

      It's all about trade offs, would you sacrifice your right to kill people in exchange for being able to walk down the street in relative safety? If there was nothing to stop them, i imagine some people would try to kill you just for disagreeing with them online...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    13. Re: Re:just.. wow by TheRaven64 · · Score: 2

      Which library you end up using is irrelevant. Utilisation rates may be higher (and probably are) for many closed source programs. They are irrelevant to a discussion on source code freedoms and rights.

      Absolutely not. The fact that I am writing a Free Software application, and the GPL specifically prohibits me from incorporating code released under that license is precisely the issue of relevance. It is the fundamental difference between the GPL and be BSDL. The GPL aims to make writing proprietary software difficult and, as a side effect, makes writing Free Software harder by being incompatible with a huge list of Free Software licenses. The BSDL aims to make writing Free Software easier, and as a side effect makes writing proprietary software easier by being compatible with a huge list of proprietary software licenses.

      Yes, you've come up with a cocktail of incompatible licenses, most of which allow for binary-only redistribution, something the GPL does not allow you to do. "AHA!" I hear you say, I'm not allowed to do that, so I have lost a freedom!

      No, I've come up with a cocktail of compatible licenses and one incompatible license. APSL, APL, and MPL are all mutually compatible, only the GPL is incompatible. Code under any of these licenses can be mixed freely. People downstream are free to modify the code in any way that they wish (one of the FSF's four freedoms), including adding code under other licenses and redistributing the results (another of the FSF's four freedoms). Until, that is, one of the things they want to incorporate is GPL'd. Then they have to either rewrite it or use something different.

      The 'allows binary redistribution' issue is a red herring that GPL advocates love to shout about. The freedom to distribute binaries exists, but in this case I am not trying to exercise it. I am trying to write Free Software, which will be distributed in source form, under FSF approved licenses. The GPL makes this harder.

      Very often, faced with this choice, people pick a proprietary alternative. I've consulted at a few companies that have made exactly this choice when it comes to their in-house software. If there's a BSDL library that does what they need, they'll use it and send back patches. They won't touch GPL'd code, and so they buy proprietary libraries rather than use GPL'd code. They have less freedom and the Free Software ecosystem loses out on their contributions.

      If I could only include GPL source code in my proprietary application then I could benefit all sorts of people, charge them for the privilege and never give them the source. But the GPL prevents this and the original author thought that the continuing openness of derived and redistributed versions of their code was more important than the ability for a wider audience to reuse it.

      Again, you go off at a tangent. I am talking purely about the case where I, a developer, wish to write Free Software, and the GPL - a license intended to promote Free Software - makes this harder. Your argument in favour of the GPL was that it removes some freedoms from the immediate recipient (i.e. me), but in return grants greater freedoms to people downstream from me. I am arguing that this is not the case.

      The people downstream from me lose out, because I have to waste time working around the GPL, or simply not distribute my work. They get no more freedoms from the GPL, because I am not choosing to restrict their freedoms when I release code under another license. Their loss is real, but their gain is purely hypothetical.

      This is not a hypothetical situation. According to Ohloh.net, my contributions for Free Software add up to over 300,000 lines of code, and I won't touch GPL'd code anymore, because doing so has caused me these problems in the past.

      --
      I am TheRaven on Soylent News
    14. Re:just.. wow by Eunuchswear · · Score: 2

      So, how long does your battery last?

      --
      Watch this Heartland Institute video
  2. Why close it now? by kvvbassboy · · Score: 2

    Symbian division is gonna be shutdown within the next 2 - 3 years. What's the point of closing it now?

    1. Re:Why close it now? by Anonymous Coward · · Score: 5, Insightful

      To ensure that it really dies, instead of some roque developers actually making it an viable option?

    2. Re:Why close it now? by Locutus · · Score: 4, Insightful

      Just remember who they signed a billion plus dollar contract with and you have your answer. Part of the cleanup and part of the plan to make sure Nokia is dead in 5 years and everything goes to the partner. IMO

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  3. Re:Next by Anonymous Coward · · Score: 5, Informative

    Rock on, bitches:
    http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php

  4. I'm scared by vgerclover · · Score: 2

    Really, I like KDE. I like QT. I'm started to feel like Nokia is becoming something awful. I hope that if anything happens, KDE has enough developer power to keep QT going.

    Yeah, I know: this is about Symbian, but really, does anyone think that Nokia is going to be working towards an Open (Source, not business) future?

  5. Borg assimilation in progress by Anonymous Coward · · Score: 5, Interesting

    This is exactly what happens when a Microsoft mole takes over a company. Past example:

    -Rick Belluzo: while at HP, he announced to the press that HP would be "dumping HPUX" in favour of Windows NT (it wasn't true, and it did cause a panic of sorts). Windows NT 3.1, no less. Later, the mole moved on to SGI where he did precisely that: threw IRIX in the trash and attempted to shove Windows NT where it didn't belong. After thoroughly destroying SGI, he then moved to the Borg Cube itself, I'm sure with a big fat reward.

  6. Hey assholes ! Error 503 Service Unavailable by Anonymous Coward · · Score: 2, Insightful

    You gonna fix it this year you think? This has been going on for weeks now. You dirty incompetent fucks.

    1. Re:Hey assholes ! Error 503 Service Unavailable by vuke69 · · Score: 5, Funny

      I'm sure they'll get around to fixing it right after they get around to fixing Slow down cowboy! It has been 3 hours, 26 minutes, and 12 seconds since you last posted a comment.

      Some real rocket surgeons working at Slashdot, it seems.

      Odd... that's almost exactly the amount of time it takes between when I hit the preview button, and when it finally lets me hit submit.

      --
      Time is an illusion. Lunchtime doubly so. ~ Douglas Adams
  7. Stick a Fork in it, its done! by ramriot · · Score: 2

    Is it even possible to close an open source project? If the license allows derivatives under the same license then would not the community create a Fork and start developing from that?

    1. Re:Stick a Fork in it, its done! by the+linux+geek · · Score: 2, Insightful

      Maintaining a project the size of a complete, commercial-grade, operating system takes incredible resources. Saying "let the open-source community handle it" without commercial backers isn't viable.

    2. Re:Stick a Fork in it, its done! by the+linux+geek · · Score: 2

      What massive-scale open-source project is commercial-grade without being largely commercial backed?

  8. Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 4, Insightful

    Fujitsu. Musashi-Nakahara office, actually.

    Entire rows of programmers working late overtime, desperately trying to figure out how to get something working in Symbian. It was the most ridiculous thing I ever saw. Even more, in order to get into the office to talk to someone, you need to sign a release that permits you to view the Symbian source.

    I'm sure Symbian is a source of income for Nokia, with unimaginative Japanese companies like Hitachi and Fujitsu stumbling over themselves trying to find new ways to get a return on their 10 year "experience investment". God forbid they actually try to build something that Docomo and AU didn't order them to build - the idea of building a phone for the gigantic foreign market never hit them, apparently.

    As an side, my supervisor there was a intelligent lady who was chosen out of 400 applicants. Her response when I told her about the iPhone 2g? "Why would anyone use that? Won't it get finger prints all over it?"

  9. Good move! by Anonymous Coward · · Score: 2, Interesting

    Closing the source of such a poor operating system as Symbian may be a clever move. People might start to think that there is now some value in it. I used to program in it quite some years ago and my impression at the time (not changed since) was that it owed its position to being owned by Nokia, and being at the time was the only smart phone system on the market. Programming in it was not easy and took at least 4 times as long as programming Windows. I remember any kind of memory leak was forbidden, or the software wouldn't work. When I eliminated all the ones in my code I discovered that the OS calls I was making were themselves leaking. At that point I threw in the towel.

  10. Nokia Confirms Symbian Is... by Frosty+Piss · · Score: 2

    ...dead.

    --
    If you want news from today, you have to come back tomorrow.
  11. Re:Open by Archangel+Michael · · Score: 2

    I'm not so sure. I think Microsoft is running their playbook just fine. They even have one of their own at the top.

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  12. Re:Next by sdiz · · Score: 2, Interesting

    Actually, they are following this guide: http://lwn.net/Articles/370157/

    If Nokia close Qt, the community win.
    If Nokia keep Qt open (but make it sucks), the community is destroyed.

  13. Re:Seriously? by Archangel+Michael · · Score: 5, Insightful

    Are they TRYING to lose relevance?

    Yes. And the exec that is making the calls is going to get out with a nice golden parachute and get all his Microsoft Stock Options back, while the people who own Nokia Stock are getting screwed.

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  14. Open Is As Open Does by NicknamesAreStupid · · Score: 2

    Last year, I attended a meeting in Mountain View, CA hosted by Nokia to announce their new app store, Ovi, and 'open' platform based on JavaScript, the language everyone loves to hate. It seemed like a sincere attempt to recruit talented programmers to join a trip on the Titanic. There were a lot of sincere people making excuses and promising to do whatever it took to take on Microsoft. "We are the largest mobile phone company in the world, and we will respond accordingly," or something like that. I will say that the food was good.

    They did respond like the largest mobile phone manufacturer, sinking their 'open' platform and joining up with the largest proprietary OS manufacturer. It is like a binary star system imploding into a black hole. Ironic, too, since Microsoft will buy RIM in Q4 for $39B, effectively screwing this deal. If this were fiction, then nobody would read it. Reality has such a wonderful way of making an acid trip seem like a lukewarm bath.

  15. Amazed by Trogre · · Score: 2

    I'm still amazed at how the Microsoft trojan managed to work his way into Nokia so effectively. Someone must have let it happen.

    Does anyone have any ideas as to what could have happened?

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    1. Re:Amazed by dbIII · · Score: 2

      I'm amazed that the shareholders haven't dumped him yet. I'm sure the government over there is also getting twitchy and thinking of looking for an angle before they lose the biggest source of export income their nation has. With software coming from the US, dropping about 90% of their current market (by requiring expensive hardware to run the MS software) and manufacturing from China there isn't much for Nokia to do in Europe apart from being a mailbox.

    2. Re:Amazed by mcvos · · Score: 2

      I'm amazed that the shareholders haven't dumped him yet.

      This.

      I'm sure the government over there is also getting twitchy and thinking of looking for an angle before they lose the biggest source of export income their nation has.

      And that.

      I really don't think there's anyone on the planet other than Microsoft and one particular ex-Microsoft employee, who is happy with Nokia's new direction.

    3. Re:Amazed by belgianguy · · Score: 2

      Woops. Saw I posted this as an AC.

      Nokia was blindsided by Android. Instead of adopting it and riding its wave of success, they thought they stood a chance with their own line of products. For too long they ignored that Android was far more popular than what they had to offer. I think they didn't dare to go the Android way as it would compete directly with one of their own products (Symbian/MeeGo), making them look foolish and not competent at producing their own products. So I guess they hoped to stay relevant on their "century-old, great phone, yadda yadda" image. The day they realized this wasn't the case, it was already far too late, and panic set in.

      And panic rarely leads to well thought out decisions. They needed a lifebuoy if they wanted to stay relevant. Microsoft seized the moment (as they needed someone to sell their bloat) and this allowed them to sneak an eel in (Elop). To no-one's surprise, he's hollowing out the phone giant to the point where the once big Nokia will be nothing more than a "one size, fits all, doesn't update" phone manufacturer. Everything else Nokia had will eventually disappear or implode by the weight of the dust that will gather on it. Nokia will rely on Microsoft like a junkie relies on his dealer: when the next fix doesn't come, the gutter awaits. Windows or die.

      I hope Qt can be saved/extruded from this mess. It would be a damn shame to see MS scuttle it in favor of cramping .NET down some more throats.

    4. Re:Amazed by kikito · · Score: 2

      Somebody gave somebody lots of money.

  16. Re:Next by Hognoxious · · Score: 2

    This actually makes me respect KDE a little more

    Not being Gnome isn't enough?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  17. Re:Nokia who? by mcvos · · Score: 4, Insightful

    That's only because their older phones are practically indestructible. Nokia seems rather determined to be on the way out at the moment.

  18. Re:Open by TheRaven64 · · Score: 2

    They made almost two billion in profit last year. Microsoft paid them another billion to use Windows Phone 7 this year. They have about 15 billion in liquid assets (cash and short-term investments). They'd need to be spectacularly incompetent for a long time before they hit bankruptcy.

    Nokia doesn't seem to be dying as a company, just dying as an interesting company.

    --
    I am TheRaven on Soylent News
  19. Re:Next by calagan800xl · · Score: 2
  20. nothing to do with the Microsoft deal by doperative · · Score: 2

    I guess this has nothing to do with the Microsoft deal :)

  21. Re:Seriously? by Rich0 · · Score: 2

    Yup, the reality is that little that is done in major companies is done primarily for the company's benefit. What happens, happens because it will make a manager somewhere better off in some way (financially, psychologically, whatever). To the extent that company well-being is actually tied to rewards that may happen to also benefit the company, but that is usually a secondary consideration.

    When some manager comes up with some crazy mandate that everybody knows will hurt the company, do they all raise a big protest? No way! They all get in there and write up at the end of the year how enthusiastically they implemented it so that they can collect their annual bonus. Then, when the next manager enthusiastically reverses the policy of the first one, everybody enacts that policy with equal vigor. Being bad for a company will never slow down a big initiative. Now, if the big initiative is bad for individual employees, then it will meet with resistance regardless of impact on the company.

  22. Re:Nokia who? by jimicus · · Score: 2

    Really? I don't know if it's different where you are, but here in the UK Nokia's presence in all the big phone stores is seriously down over the last 6 years.

    They're not dead by any means, I grant you, but the days when everyone and his dog had a Nokia 3310 except for business users who were given a 6210 are long gone.