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.''"

246 comments

  1. Nokia who? by Anonymous Coward · · Score: 0

    Are they still around?

    1. Re:Nokia who? by Anonymous Coward · · Score: 0

      Most mobile phones out there are still Nokia.

    2. Re:Nokia who? by AHuxley · · Score: 1

      They made tyres, paper and had some telco interests.

      --
      Domestic spying is now "Benign Information Gathering"
    3. Re:Nokia who? by bmo · · Score: 1

      And boots.

      Nokian studded bicycle tires can't be beat for riding on ice.

      I think the only business they'll have left is their rubber products

      --
      BMO

    4. Re:Nokia who? by Anonymous Coward · · Score: 0

      Shhh.... don't try and buck the Slashdot groupthink. Remember, we don't like Nokia round here. They're like Microsoft, so they are bound to be out of business in a year or two.

    5. Re:Nokia who? by White+Flame · · Score: 1

      And they made some great CRTs back in the day.

    6. 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.

    7. Re:Nokia who? by testadicazzo · · Score: 1

      I still have a Nokia television.

    8. 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.

    9. Re:Nokia who? by bill_mcgonigle · · Score: 1

      Nokian studded bicycle tires can't be beat for riding on ice.

      Oh, no, reminds me of College!

      I think the only business they'll have left is their rubber products

      The companies split in '88. I did have some Nokia tires at one point, but the next set were Nokians (the WR series is still a great buy).

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  2. 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 gstoddart · · Score: 1, Insightful

      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.

      Some might argue that OpenBSD is more "open" than the GPL is.

      The GPL places restrictions and obligations upon you ... the BSD people make no such restrictions. If you want to bundle it up into a project and sell it, go right the hell ahead.

      GPL'd software is almost essentially 'emancipated' in that it is now 'libre' ... BSD software is 'free' and 'open', but doesn't have any rights of its own, but I as someone who wants to use it am totally free to do as I please.

      There's a reason that people who release under a BSD license are some of the most consistent supporters of fully-open systems ... but it's an ideological difference with the FSF whereby if you can crib some good software to make your software better, we all benefit. In fact, you have our blessing. Even if that means you don't want to give back what you've done with it.

      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.

      I applaud people who release code under a BSD license, since it basically says "go forth and write cool shit, you don't owe us anything".

      --
      Lost at C:>. Found at C.
    3. 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.

    4. Re:just.. wow by internettoughguy · · Score: 1

      I think that the GPL is too restrictive in cases where the software components are highly reusable and might be handy for a proprietary project; but that's where the LGPL comes into play. To me the BSD licence seems like a wasted effort when you're coding in your free time, as there's simply not enough "encouragement" for proprietary developers to contribute to the project, at least with the LGPL if they fix or modify something in your code then they are compelled to submit those changes before redistributing your code.

      The BSD has it's place though, and you're point is valid, it is more open than GPL, and in some ways BSD'ers are even more generous with their time than GPL'ers, perhaps they're just a little too generous at times :).

    5. 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.

    6. Re:just.. wow by gstoddart · · Score: 1, Insightful

      But if you're going to start casting stones, you might want to check the ground you're standing on before you start.

      My stance on the relative difference between GPL and BSD, and when they're comparatively "better" has been fairly established since the late mid-to-late 90s.

      I don't care about how you perceive BSD fans nowadays as I'm not the one making those statements. And, I can't tell you how often I see GPL people talking like Communist revolutionaries who are obsessed with the ideology ... "it's more free because it's libre" ... and you guys whine about the Apple people wearing black turtlenecks and doing beat poetry? I've thought RMS was a bit of a crank since I hear him speak in 93.

      I've both used BSD code in commercial software and submitted bug-fixes to GPLd code. They each have their place and their application -- I'm in favor of both of them.

      That doesn't mean there aren't times when I'm not grateful to be able to take some really useful piece (BerkelyDB, for example) and building something useful with it because it accomplished a lot of the plumbing to build something on top of it without worrying about if I'm legally covered. Or, grab a copy of Linux and set up a server.

      I think the notion that there is one "correct" form that "free software" can take is mostly rubbish.

      --
      Lost at C:>. Found at C.
    7. Re:just.. wow by gstoddart · · Score: 1

      The BSD has it's place though, and you're point is valid, it is more open than GPL, and in some ways BSD'ers are even more generous with their time than GPL'ers, perhaps they're just a little too generous at times :).

      But, at the end of the day ... it is their time, and their code. So your opinion about how someone else allocates their labors is irrelevant.

      The arrogance of someone to say "how dare you give away software that someone doesn't have to give to the end user" is exactly why I say that some really staunch GPL advocates are worried about the ideological purity of code.

      Essentially, those people would impose their own ideology on the people who would release under a license which didn't place obligations on someone else. In effect, telling them they're wrong.

      The GPL is a political ideology, and those who most strongly advocate it would claim that their ideology is better than someone who wants to be "free" in the sense that I can take it and do as I please.

      I'm not saying both don't have their place, I'm saying that GPL to the exclusion of BSD (or the reverse) is completely unnecessary. Rabid *-ism is stupid in all of its forms. The GPL is no exception.

      --
      Lost at C:>. Found at C.
    8. 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.

    9. Re:just.. wow by Anonymous Coward · · Score: 1

      And those some would be wrong.

      Hardly. You make a nebulous argument about end users (for whom by and large, code is useless - sorry, Slashdotters, you are atypical) and freedom, while ignoring the rights of software producers and freedom.

      The fact that the GPL throws chains upon developers - noble intentions or not - easily counters the, "But the users!" argument.

      I submit BSD and GPL are equally free, if different.

    10. Re:just.. wow by Anonymous Coward · · Score: 0

      Really, man? This shit again? And you got modded insightful. Should be negative a brazilian redundant.

    11. 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.

    12. Re:just.. wow by Anonymous Coward · · Score: 1

      How is it less free for third parties? Is there an inherent right to source code? The BSD code is still there in all it's glory to modify and use as you wish. Unless there is an inherent right to source code then you do not (unless the license specifies it, such as GPL does) have any right - and therefor loose no freedom - to the changes the second party makes to the code.

      You can't force freedom - ask the US govt how well that works, no different here. It is true by definition. That doesn't mean the GPL is Evil, I generally choose GPL over BSD for anything I have done but I do not fool myself into thinking I'm doing anything other than telling someone they have to do something to use the IP I chose to not charge money for (the subsequent releasing of their code/IP is the payment for use).

      You are not free to tinker with your PS3 for other reasons, those reasons *are* wrong. You should be free to tinker with it all you want - you purchased it and it is yours (that should be, in fact, an inherent right). In fact, for the most part, releasing the source code ala GPL wouldn't make it suddenly legal to tinker with it either, you would just know what was happening better. Look an the Motorola Android phones - bootloader locked down and illegal to modify by the same license even though the base system is GPL. In fact, if we assume your definition of "freedom" is what the GPL is about then it failed fairly miserably. Of course others saw that too and thus v3 of the GPL, but that got watered down due to reality (people can choose not to use your software or accept your license - make it too draconian and few will use it). RMS certainly had that goal, but there are others involved in the GPL too.

      They both have their place, however BSD certainly has less restrictions and that is generally the definition of "freedom" or most people. Open Source is a great term for GPL, not "freedom".

    13. Re:just.. wow by exomondo · · Score: 1

      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.

      That's why i prefer BSD-style licenses, they are more altruistic, it's not about forcing people to do things your way. With the GPL it's more of a 'you can freely use my code within the scope of my idea of freedom' whereas the BSD is a 'you can freely use my code'.

    14. Re:just.. wow by Anonymous Coward · · Score: 1

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

      Wrong. 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. BSD and GPL licenses have their plus and minus points, however GPL has more restrictions (perhaps with laudable aims) and is less free for all users of the code, who are restricted in their actions.

    15. Re:just.. wow by exomondo · · Score: 1

      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.

      That's only one possibility, and it's likely that without that BSD code the would have written their own (incompatible?) code instead. So the only loss is the potential interoperability, and if there is no interoperability then nothing is lost.

      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.

      Someone taking BSD code and marrying it with their own proprietary code doesn't do anything to the original code, that code is still there and free to be tinkered with and learned from. GPL just forces everyone else who wants to use that code into that way of thinking.

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

      That's a fair point, but in truth the bit you want to tinker with is the proprietary code, the BSD code is still free. So you want them to release their code under a free license as well.

    16. Re:just.. wow by exomondo · · Score: 1

      I think the notion that there is one "correct" form that "free software" can take is mostly rubbish.

      Neither is more 'open' or more 'free', the only fact is that one is more restrictive than the other. BSD is much more altruistic, the GPL is more about supporting an ideology, which is 'better' depends on your point of view.

    17. 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?
    18. Re:just.. wow by Nursie · · Score: 1

      Someone taking BSD code and marrying it with their own proprietary code doesn't do anything to the original code, that code is still there and free to be tinkered with and learned from.

      Not when it comes on a closed up device, with no way of running it on that device and likely not even an indication that there's even any BSD code in there.

      So, I as a recipient of BSD code in binary form - I might not know it's BSD, the original project could have disappeared or gone offline, all sorts of stuff. To say it *never* goes away is simplistic. The GPL grants this right, BSD does not. RMS would term this right one of his "fundamental freedoms", but then he does talk out of his fundament quite a lot :)

      GPL just forces everyone else who wants to use that code into that way of thinking.

      That's a fair point, but in truth the bit you want to tinker with is the proprietary code, the BSD code is still free. So you want them to release their code under a free license as well.

      Actually it's neither. As a consumer I want to tinker with my device. As a FOSS developer (very small scale hobby) I want people who receive my code and things derived from my code, usually itself minor additions to other projects, to have the same rights I did. The right to ask the binary distributor for the source, and usually also the infrastructure (build systems etc, if not the software tools) to play around with it. It's not that I demand the right to use other people's code, it's that they have to play ball if they want the right to use mine.

      I respect that the BSD author's wishes are to release code the way they do, so I'm not going to give you a list of "They should have done it my way!" items because that's nonsense.

      I don't think either is necessarily superior in terms of freedom. The GPL just suits the freedoms I want for myself better than BSD does. If you like to think of BSD as more altruistic as a result then that's up to you, but if you look at the software ecosystem (particularly consumer devices with embedded operating systems) you'll see that the GPL often opens up a lot of areas of cool hobby-type stuff that would have stayed closed if there was no publishing requirement for linux. Not because companies are necessarily 'evil' or closed, but because it's at least a minor hassle and a minor cost to pull together that source tarball and shove it on your website, so nless you have to, why would you?

    19. 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.

    20. Re:just.. wow by dbIII · · Score: 1

      It's only a dying platform because it's been murdered while the new CEO wrecks as much as he can with the goal of making Nokia small enough to easily take over.

    21. Re:just.. wow by Darinbob · · Score: 1

      There is no restriction with BSD. No one can take it and lock you out of it. All they can do is fork a branch and close that off. Anyone can tinker with BSD code.

    22. 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.

    23. Re:just.. wow by Anonymous Coward · · Score: 1

      > The BSD code is never lost.

      That may be true for the BSD code itself. But I am nearly certain that there is BSD-licensed code somewhere that was once available and was lost (server becoming unavailable etc). I wouldn't even exclude that that same code might still be available in binary form in a currently maintained commercial product.
      Though this corner-case isn't _really_ the point of GPL.
      However it should also be noted that some companies when they start contributing aren't willing to contribute with anything more liberal that GPL because they are afraid that competitors "take their code and run with it".
      (Before I get flames: only making a counter-point here, use whichever license you want. For me that is usually whichever license the original project is and for my own irrelevant stuff GPL or LGPL).

    24. Re:just.. wow by Nursie · · Score: 1

      Fork it off. Close the branch, modify some of the loading code, sell you a closed device running it with no way for you to alter it or even really figure out what's going on inside. Original project drops off the 'net... what now?

      As an (infrequent) FOSS contributor, I believe in granting freedoms to the consumer (i.e. also me) rather than the manufacturer (Sony, cisco, WD etc etc). This is the BSD/GPL freedom trade off.

    25. Re:just.. wow by Anonymous Coward · · Score: 0

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

      You say that like the code that the first party received is somehow destroyed after they get it. It's not.

      GPL = You can modify the code with the restriction that you also release your modifications under the same license.
      BSD = You can modify the code without restriction.

      BSD is more free.

    26. Re:just.. wow by LordVader717 · · Score: 1

      Flamewars aside, GPL advocates will certainly have an opinion on the issue, but I don't think very many of them wouldn't give credit to people willing to release their code as BSD or Public Domain. As you say, it is their choice.

      On the other hand you do indeed have people who criticize GPL developers and the like for not giving away more, instead of being thankful for the gifts they do receive. Along the lines of "this is great, but it would be great if you could release it under BSD".

    27. Re:just.. wow by wvmarle · · Score: 1

      Risking off-topic mods here but OK can happen.

      BSD license I know what it's doing, it's simple.

      GPL I also know the basic features of.

      Google uses the Apache license for lots of their Android related stuff; Firefox has the Mozilla license; and so there are many more. Those I don't know much about - but am interested to know about. I find the GPL quite restrictive too; BSD maybe a bit too free.

      I'm looking for a simple, laymen style, non-legalese write-up of what those licenses basically do. Any suggestions?

    28. Re:just.. wow by Nursie · · Score: 1

      BSD - As someone handed a binary blob of stuff, the guy that gave it to me doesn't even have to tell me where he got it from, let alone provide me with the source

      GPL - As someone handed a binary blob of stuff, I have the freedom to explore and alter the source of that program

      GPL is more free.

      (Yes, this is simplistic, but I'm responding to your stupid argument with an equally dumb one. Anyone saying either one is inherently more free is wrong. They provide different freedoms to different peopel)

    29. Re:just.. wow by wvmarle · · Score: 1

      For end users, for most practical reasons the license on the code doesn't matter. Most of them don't even know what license the software they use has. They just use it.

      For developers (whether professional or hobby) it does matter of course.

    30. 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.

    31. 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.

    32. 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
    33. Re:just.. wow by JasterBobaMereel · · Score: 1

      You can change BSD licenced code to closed, and people still have the open code

      You can change GPL licenced code to closed, and people still have the open code

      from this point of view they are as open as each other

      --
      Puteulanus fenestra mortis
    34. Re:just.. wow by testadicazzo · · Score: 1

      I don't agree with your assessment that RMS is a zealot. I think this news item just shows that RMS was right -- if we forget that the Free Software is about freedom, and just focus on whether or not the source is open, we allow the parasites a foothold, which they will use to maximize their profits and erode our freedom. It becomes a mechanism by which corporations steal the labor of the creators -- they steal it from the community by robbing us of our freedoms.

    35. Re:just.. wow by TheRaven64 · · Score: 1

      Okay, I have three libraries, one licensed under the Apache 2.0 license, one under the Apple Public Source License 2.0, and one under the Mozilla Public License. I use them all in a program that I've written, which I can distribute under any license I choose. I decide to release it into the public domain. Then I want to incorporate some more functionality. There are two versions of a library that does what I want, that are functionally equivalent. One is GPL'd, the other is BSDL'd. Which one should I pick?

      The answer, of course, is the BSDL one. Why? Because if I pick the GPL'd one then I do not have the right to distribute the complete program to anyone. So tell me, what freedom did the GPL'd code give me, or people downstream from me, that the BSDL didn't give? I'm writing Free Software (all of the licenses that I listed are on the FSF's approved list of Free Software licenses), but if I incorporate GPL'd code then I am no longer allowed to distribute my work. Who benefitted from this? According to your argument, the people I distribute my code to, except that with the GPL, there aren't any of these people.

      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.

      Exactly the same applies with the GPL. The binary distributor only has to provide an offer, good for three years, to provide the source. If no one requests it (in writing), or if no one who requested it publishes it, then it's lost.

      --
      I am TheRaven on Soylent News
    36. Re:just.. wow by TheRaven64 · · Score: 1

      BSD - As someone handed a binary blob of stuff, the guy that gave it to me doesn't even have to tell me where he got it from, let alone provide me with the source

      You've posted in this thread a load of times, but you obviously haven't actually read the BSDL. It's only 2-4 clauses (depending on the version you read), so it shouldn't take more than a couple of minutes. I suggest that before you argue about the merits of various licenses, you actually try reading them...

      --
      I am TheRaven on Soylent News
    37. Re:just.. wow by Nursie · · Score: 1

      "You've posted in this thread a load of times"

      Because so far 9 people have replied to my original post.

      "but you obviously haven't actually read the BSDL"

      I've read the BSD license several times before. The copyright notice and BSD license must be reproduced when binaries are distributed. Likely on page 400 of a manual that's probably online somewhere or on a cd rather than printed anywhere with the device.

      It doesn't mandate telling you where the guy giving you the binary got it from, just a namecheck on the copyright holder. Neither does it give the right to ask for source.

      So what exactly did I get wrong in my post?

      "I suggest that before you argue about the merits of various licenses, you actually try reading them..."

      And I suggest that before you interject you have something to say.

    38. Re:just.. wow by Bert64 · · Score: 1

      There's nothing to stop a commercial vendor from taking BSD code and creating their own intentionally incompatible closed source fork of it either, no guarantee of interoperability at all. At least if someone does that using GPL code, its easier to reverse engineer the changes they made.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    39. Re:just.. wow by devent · · Score: 1

      "GPL pretty much forces closed source to make their own implementations of standards, which may or may not be 100% compatible."

      Why is that a bad thing? A standard is only a standard if there are multiple different implementations. Also, BSD code opens up closed source code to modify the standard to their whishes with very little work of their own. With GPLed code I at least have the right to fix a broken implementation, with closed up BSD code I don't have the right. It's then nice to have BSD code that implements the standard 100% only to be forced to use an application that just takes the BSD code and modifies the implementation just a little in a way that I'm stuck with this one application.

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    40. 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!
    41. Re:just.. wow by Anonymous Coward · · Score: 0

      Having the metafreedom to reduce your freedoms is tantamount to not really having the freedom as you can just accept money to agree to waive your rights. Hence BSD's 'more freedom' through metafreedom is actually less.

    42. Re:just.. wow by Nursie · · Score: 1

      "The answer, of course, is the BSDL one. Why? Because if I pick the GPL'd one then I do not have the right to distribute the complete program to anyone.

      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.

      So tell me, what freedom did the GPL'd code give me, or people downstream from me, that the BSDL didn't give?"

      You are not the the recipient of the freedoms, just someone using a whole mess of licenses to try to stitch together some software.

      I'm writing Free Software, but if I incorporate GPL'd code then I am no longer allowed to distribute my work.

      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!

      But wait, if that is allowed then it is possible that users lose freedoms later. The person writing the original GPL component though that that was *more* important than you being able to use it.

      "Who benefitted from this? According to your argument, the people I distribute my code to, except that with the GPL, there aren't any of these people."

      Again, irrelevant.

      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.

      Exactly the same applies with the GPL. The binary distributor only has to provide an offer, good for three years, to provide the source. If no one requests it (in writing), or if no one who requested it publishes it, then it's lost.

      All true, but still irrelevant because the 3 years is 3 years more than the promise of source from someone that hands you a binary from BSD sources.

      Some folks who consider that your pragmatic stance is more important than having the entire ecosystem under GPL-like source code availabilty conditions will use the LGPL precisely to help folks like you out. Others won't. It's their freedom to choose I guess....

    43. Re:just.. wow by Nursie · · Score: 1

      To be honest I don't usually like it when people use dictionary definitions in internet arguments, but it helped me to clarify whether it was right or not. First definition from a google search on "zealot definition":

      . A person who is fanatical and uncompromising in pursuit of their religious, political, or other ideals.

      He is uncompromising, most certainly, and will not use closed systems to the extent of seriously inconveniencing himself. Fanatical? Well, unsure. I might have to look at another definition there. So perhaps he is and perhaps he isn't.

      He certainly displays zeal for his FOSS ideals, he is at the least an idealist rather than a pragmatist. not something I have a problem with necessarily. I don't buy into all of his arguments though.

    44. Re:just.. wow by Anonymous Coward · · Score: 0

      Why don' t you simply distribute the GPL library on its own?

    45. Re:just.. wow by Anonymous Coward · · Score: 0, Interesting

      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.

      GPL is like giving a gift but demanding that the gift is not used to harm anyone else rights to enjoy of it.
      BSD is like throwing out own stuff and someone might find a something from it to give someone without the rights or joy.

      It really matters that _everyone_ gets same freedom rights and no one can rip it off.

      So actually:

      GPL is like everyone are free and slavery is not allowed as slaves are not free
      BSD is like everyone talks that they are free, but some people makes others as their slaves and keep them in slavery but same time talking how they are allowed to slave others.

      Which one is freedom?

      GPL is like world without slavery where every person has same rights and there is no difference between rich and poor, healthy and sick, old and young etc.
      BSD is like world as southern USA was 1600-1800 century with black people who were brought from africa to work for white people fields because they were free to be taken from their homes in africa and white people did not want to do hard job in fields.

      Heck, even today USA is very young at the slavery thing. How long it has been when black people did get any kind a rights in there? It was 1955 when single black women toke the stand (seat actually) against race law. It is JUST 66 years ago!
      Or 1962 when first black man got rights to study in the Mississippi university and that demanded even John F. Kennedy to send a millitary on the place. And that has happended just 49 years ago! And even today, too many people believes that black people does not have same rights!

      For some twisted minded people, freedom is that people who has leverage to other people, has rights to take their freedom away and use it for own benefits. And BSD is exactly a great example for such twisted minds!
      BSD might be a open, but in this situation I stand on same level with RMS (even that I dont like him personally) that there is difference with open source and free software. And free software is much better (I prefer "Libre Software" definition) for the humanity than what todays marketing definition "open source" is.

    46. Re:just.. wow by Jurily · · Score: 1

      Flamewar time!

      BSD is concerned about the end users: "I want Microsoft to ship my TCP stack with their OS. At least it'll have one part that works." Of course, the people involved often forget that so they end up both feeling smug about being "more free" than GPL and whining about getting ripped off.

      GPL is concerned about the software development process: "I scratch your back, you scratch mine." Of course, the people involved often forget that so they end up both feeling smug about being "more free" than BSD and whining about how nobody else uses their code, and how the forest should be GPL because they saw a squirrel looking at their screen once.

    47. 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
    48. Re:just.. wow by Hal_Porter · · Score: 1

      I applaud people who release code under a BSD license, since it basically says "go forth and write cool shit, you don't owe us anything".,

      Naah, it's like Stalin said - you're not truly free unless you're chained to a millstone in the collective farm. This is why I prefer the "Freedom as in slavery" of the GPL. Orwell was right!

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    49. Re:just.. wow by TheRaven64 · · Score: 1

      In some cases, I can. I can distribute a plugin-style shim in source form, along with a script that compiles it and links it to the GPL'd code. This is exactly what nVidia does to work around the GPL in the Linux kernel. In fact, if I don't want to write Free Software then I can ship a proprietary application and (separately) ship a shim like this that loads a GPL'd library. The end result? No more freedoms for the end user than if the GPL'd code had been BSDL - they get the unmodified version, but no difference access to any of the code that I've written.

      The GPL makes life difficult for people writing Free Software, but people writing proprietary applications can easily work around it and restrict the end user's freedoms as much as they want.

      --
      I am TheRaven on Soylent News
    50. Re:just.. wow by clang_jangle · · Score: 1

      GPL is like everyone are free and slavery is not allowed as slaves are not free BSD is like everyone talks that they are free, but some people makes others as their slaves and keep them in slavery but same time talking how they are allowed to slave others.

      Can't you read? I can understand being insufficiently literate to understand the licenses themselves, but it's spelled out quite succinctly in this discussion. Are you just trolling? BSD-licensed code may be re-used however one wishes, but the original, BSD-licensed code remains forevermore open and available. That's as free as freedom gets, surpassing even Public Domain, which is at risk for being copyrighted or even patented by anyone who files an application.

      The OP has it right. GPL=="Here's a gift, what'd you get me?" BSD=="Here's a gift, hope you like it!"

      --
      Caveat Utilitor
    51. Re:just.. wow by Anonymous Coward · · Score: 0

      The licenses ensures *code* freedom, not developer freedom.

      Think of it like human rights. In one hand you have BSD and other similarly "weak" licenses. The population (code) doesn't have strict laws ensuring they won't get abused, maimed, killed, disappropriated or plucked from their homes by the government, the dictator. On the other hand you have GPL, where the population enjoys considerable liberties that protects them from such behavior. There's still a dictator, but what he's allowed to do is limited by the license.

      As a dictator it's much much more convenient to have a BSD populace, since they're more akin to subjects or slaves. The government is free to do whatever it wants with them. You may have been free (gratis) at one point, but one day you may wake up as proprietary. As a citizen you'd much rather prefer to have GPL cover your back though; that way you're free (libre) and you'll stay free forever.

    52. Re:just.. wow by clang_jangle · · Score: 1

      I submit BSD and GPL are equally free, if different.

      Only if you redefine "free", which oddly enough is what the GPL tries to do. :)

      FWIW I have published code under a number of closed and open licenses. The only reason I ever publish anything GPL is because I'm reusing some GPL code. Otherwise (if it's not a for-profit project) I'd use only BSD-licensing, as it's as close to unconditionally free as one can get without risking someone else claiming it as their own and closing it off (as can happen with PD). BSD-licensing is definitely more free, it really isn't debatable at all without the common GNU trick of redefining "free".

      --
      Caveat Utilitor
    53. Re:just.. wow by Anonymous Coward · · Score: 0

      The GPL doesn't mean that you have to release modifications - only if you're distributing it.

    54. Re:just.. wow by Anonymous Coward · · Score: 0

      Accurate and succinct. Mod it up!

    55. Re:just.. wow by Anonymous Coward · · Score: 0

      GPLv3 is like a gift to mankind. It will arrive at anyone while still being a gift and useful if it arrives anywhere else. Anyone receiving it however has no obligation to pass anything on, the conditions merely apply if they do.

      BSD is like a gift to some company or developer primarily. Most likely the majority of mankind won't be able to use it directly because it is locked down under some DRM or otherwise unusable except by said company or developer's sanction.

      Less nice way to put the situation

    56. Re:just.. wow by Jeff+DeMaagd · · Score: 1

      There are other sides to the situation. The difference is that third parties use code and benefit from other people's work without ever contributing anything back. Some people see that as a problem, and I understand why they would.

    57. Re:just.. wow by voss · · Score: 1

      Actually that metaphor doesnt quite work. Ideologically, GPL is like community toolbox where people can borrow tools but also have to contribute tools and let people know what tools they were using. BSD is like making a toolbox filling it with tools and putting a sign on it "help yourself".

    58. Re:just.. wow by Anonymous Coward · · Score: 0

      Yes, because murder is exactly the same thing as lines of code.

      Man, get a grip on reality.

    59. Re:just.. wow by drinkypoo · · Score: 1

      That's a lot of nonsense. Symbian was a dying platform anyway because phones are getting so much more powerful so quickly. You don't need an OS that fits in a tiny corner of a shitty core if you have a big fancy multicore with a GPU.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    60. Re:just.. wow by DrXym · · Score: 1

      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...)

      I dunno. If someone wrote a decent Symbian / QT layer for Android it might prove useful if only for all those app developers with swathes of Symbian code looking it to migrate it somewhere.

    61. Re:just.. wow by Eunuchswear · · Score: 1

      Score 3, funny.

      But

      It 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.

      This is out-of-the-blue offtopic/trolling/flamebait.

      Just look at the replies.

      --
      Watch this Heartland Institute video
    62. Re:just.. wow by Eunuchswear · · Score: 2

      So, how long does your battery last?

      --
      Watch this Heartland Institute video
    63. Re:just.. wow by Fast+Thick+Pants · · Score: 1

      Some asshole said he was "open" but he was only open for business

      I prefer the term "free as in for sale".

    64. Re:just.. wow by sleepy_weasel · · Score: 1

      The only problem I really see with the Linux folks is that they'll happily take BLOBs (binary drivers) from companies like Texas Instruments, Nvidia, and the like. The LInux devs will happily sign NDAs and wait patiently for those companies to support Linux. Sure, you may get a driver that works with your graphics card, but when you get a bug, you have to hope that those same companies care enough to fix it. OpenBSD devs will NOT sign NDAs, or incorporate BLOBs into their kernel or userland. And when they ask for support from companies, they ask for documentation, and hardware donations. They don't ask for code.

      Companies don't often want to give out documentation, because "those linux folks are happy with our table scraps, why can't you be?"

      So the OpenBSD devs had to create an Nvidia driver from scratch. It took time and effort, but in the end, the OpenBSD nvi driver is better for the most part than Nvidia's... Why? Because you can look at OpenBSD's code. It can be scrutinized. It can be easliy fixed and patched without a lawyer knocking on your door. You can take that driver and incorporate it into a linux build if you wanted.

      It's unfortunate that just because OpenBSD doesn't have flash, that folks turn a blind eye to it.

      --
      It's all damned lies and statistics!! I mean 47% of all people use statistics to back up their arguments.
    65. Re:just.. wow by Kjella · · Score: 1

      Last statistics I saw, 90% of programmers were employed on in-house projects that are never intended for distribution.

      In the traditional sense, no. But you can end up in various issues with subsidiaries/spin-offs/joint ventures/outsourcing/whatever to make sure your software is never legally distributed. And at least in many companies there's our code and licensed code, just because someone can pick up a GPL'd library doesn't make it "their" code. You have to track everywhere it's used so it doesn't end up in anything you DO distribute. That might work for isolated libraries, not so great for random bits of code in your MLOC project. It's certainly a helluva pain if you ever want to sell your software assets, buying a GPL-tainted codebase is damaged goods - even worse if you've lost control and let GPL code spread wildly, then you can't really assume any code is now safe to use for anything else.

      --
      Live today, because you never know what tomorrow brings
    66. Re:just.. wow by Anonymous Coward · · Score: 0

      As a respectable AC I don't agree on the "interoperability between ALL types of projects" part.

      BSD allows companies to tweak the original code without contributing their changes back to the community.

      So it could've been possible for MS to alter the BSD (darpa :)) IP stack without even documenting their changes (let alone pushing them upstream), resulting in an incompatible implementation.
      Merely referencing the BSD license would've been enough to comply.

      You're right that with a GPL license the "proprietary only" companies are forced to re-implement everything, but at least they can't benefit from the community implementation while still producing an incompatible implementation.

    67. Re:just.. wow by mwvdlee · · Score: 1

      The summary is; GPL expects something in return, BSD doesn't.

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

      I have a shitty LG crapfone so my battery lasts over a week of not doing anything worth mentioning. Apple has proven that it's possible to get decent battery life out of a phone that does a lot, though. Also, in the modern world recharging is just not a real problem, there are too many opportunities and technologies for accomplishing it. Unless, of course, your device won't work through a full day's hard use.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    69. Re:just.. wow by Eunuchswear · · Score: 1

      Unless, of course, your device won't work through a full day's hard use.

      Ah, how did you know I have an N900? :-)

      --
      Watch this Heartland Institute video
    70. Re:just.. wow by ekgringo · · Score: 1

      Could you please rephrase that as a car analogy?

    71. Re:just.. wow by marcosdumay · · Score: 1

      "I guess it depends on your mindset."

      Mindset and objectives. Out of those, there is no right answer. But there are a few (and vocal) anti-GPL trolls that think their way is the only way.

      I'd say there is no point on disagreeing with trolls, but that is factualy wrong. If you don't disagree, less informed people will think there is consensus on the minoritary opinion, and won't go looking for what is right. There is plenty of point on arguing with vocal trolls, it is just that you should keep in mind that they are trolls while you arguee.

    72. Re:just.. wow by bill_mcgonigle · · Score: 1

      If there was nothing to stop them, i imagine some people would try to kill you just for disagreeing with them online...

      There's nothing to stop them from doing it now. They may suffer retributive justice, but in a governmentless society they'd likely not survive [long beyond] such an attack anyway. If they're crazy enough to kill people over an online comment they're not going to be thinking so far ahead.

      Oh, no I did I just disagree with you? ;)

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    73. Re:just.. wow by MikeBabcock · · Score: 1

      I prefer to say that the GPL preserves future openness in the way that basic laws preserve the individual's right to most choices by outlawing robbery, murder and other personal-freedom restricting acts by others.

      The BSD license is more like complete anarchy. But like most people, I prefer basic rules in place to preserve my freedom for the future by imposing some limits on others' actions.

      --
      - Michael T. Babcock (Yes, I blog)
    74. Re:just.. wow by MikeBabcock · · Score: 1

      To be fair, the lgpl exists for specifically the purpose of things like zlib and libpng and other interoperability libraries. It doesn't require the open licensing of the linked binary, but direct changes to the library itself must remain open. I do sympathize with the use of MIT or BSD licenses in some cases, but for long-lived public-serving code I prefer lgpl or pure gpl. GPL purists who dislike the LGPL do not have my sympathy, and people who don't recognize the value in proprietary code don't either, although it better be really good code if you're going to package it up and hide it.

      --
      - Michael T. Babcock (Yes, I blog)
    75. Re:just.. wow by MikeBabcock · · Score: 1

      There are GPL implementations of flash that could probably be made to run on OpenBSD.

      OpenBSD has gotten a blind eye from most people over the years because its a pain to install and a pain to be compatible with. Nine times out of ten, I'd rather use OpenBSD than Linux on an internet-facing server, but nine times out of ten, Linux will run on that server easily and OpenBSD won't.

      --
      - Michael T. Babcock (Yes, I blog)
    76. Re:just.. wow by MikeBabcock · · Score: 1

      The code you write is more free under BSD.
      The code that is revised by people who used it is not.
      Many will not be able to use the revisions made by second and third parties.

      The code you write is slightly less free under the GPL.
      The code that is revised by others is equally free to the original.
      Anyone can use revisions made by second and third parties.

      A BSD licensed kernel going into a smart phone would not necessarily result in source code we could download to then work on the kernel for that phone.
      A Linux licensed kernel requires the phone company to release a source version of their kernel so we can tinker with it ourselves.

      Which of those situations looks more free to you?

      --
      - Michael T. Babcock (Yes, I blog)
    77. Re:just.. wow by petermgreen · · Score: 1

      GPL - you can freely use my code as long as you pass that freedom on and don't mix it with code that while similarly or more free differs in certain technicalities

      Not that i'm against the GPL per-se but I think that certifying as "free" licenses that are incompatible with their flagship "free" license and not making the "or later" thing a part of the license itself (leading to all the fun from GPLv3 being incompatible with GPLv2) really sends out strabge messages "you are free to use and modify program X" and "you are free to use and modify program Y" but "you aren't free to mix code from program X with code from program Y"..

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    78. Re:just.. wow by petermgreen · · Score: 1

      Symbian was a horrible platform to code for (they basterdised C++ by removing exceptions and replacing them with these things called "leaves" which didn't work correctly with RAII type structures, then they introduced another hack to try and deal with that) and while it had a web browser afaict wasn't much good. In the days before the iPhone sybian was tolerated because the alternatives weren't much better but with iOS and andriod (which is in some ways a clone of iOS) arround it rapidly started looking like crap. I don't recall their being an app store for symbian either and if there was it certainly wasn't promoted.

      Even before the MS guy got involved nokia was looking at moving away from symbian, they just couldn't seem to decide where they were going. They did several linux based experiments but couldn't seem to stick with one for long enough to make it matter.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    79. Re:just.. wow by clang_jangle · · Score: 1

      The code you write is more free under BSD.
      The code that is revised by people who used it is not.

      The way I feel about it is that's their choice to make. Why should I be automatically entitled to any revisions others want to make to the code? I prefer having freedom of choice, therefore I prefer to extend freedom of choice to others when I am able. Don't get me wrong, I admire much of RMS' work. I just don't agree with tying the idea of "freedom" to a restrictive license. It strikes me as misguided and maybe a bit hypocritical.

      --
      Caveat Utilitor
    80. Re:just.. wow by clang_jangle · · Score: 1
      Sorry, forgot to address this:

      A BSD licensed kernel going into a smart phone would not necessarily result in source code we could download to then work on the kernel for that phone.
      A Linux licensed kernel requires the phone company to release a source version of their kernel so we can tinker with it ourselves.
      Which of those situations looks more free to you?

      In spite of your GPL does anyone have the choice to run the kernel (or OS, for that matter) of their choosing on any phone currently available? There may be one or two red herrings still in production, but if so you may be pretty certain they'll be gone within a year. So this is not an issue which can be resolved by creative licensing, nor does the GPL have any advantage in this situation. GPLv3 tries to address this exact issue, with the result that no-one outside of GNU enthusiasts will touch anything GPLv3-licensed with a ten foot pole. The failure of the GPL is the failure to understand human nature.

      The BSD license doesn't try to coerce anyone into anything, which is much more in line with my personal philosophy than the well-intentioned, but frankly ill-informed GPL.

      --
      Caveat Utilitor
    81. Re:just.. wow by Americano · · Score: 1

      Most likely the majority of mankind won't be able to use it directly because it is locked down under some DRM or otherwise unusable except by said company or developer's sanction.

      No, most likely the majority of mankind won't be able to us it directly because they haven't the time, the inclination, or the skills to do so, even if every scrap of source code ever written was freely available under GPLv3-or-later copyrights.

    82. Re:just.. wow by obarel · · Score: 1

      GPL: "I'll pimp your ride, but you have to let everyone drive your car if they want to (and post the keys on the internet)"
      BSD: "I'll pimp your ride, enjoy!"

    83. Re:just.. wow by Anonymous Coward · · Score: 0

      GPL - you can freely use my code as long as you use it exactly as I want you to
      BSD - you can freely use my code including denying people from using your personally modified version

      FTFY

    84. Re:just.. wow by DarkOx · · Score: 1

      The thing is RMS thinks all software should come with the four freedoms and so do I. What the GPL is designed to do and may eventually succeed at is make so many "gifts" available to those who will be willing to release more GPL'd code (subsequent gifts to the giver and others) that it will be impossible to be competitive if you can't use GPL code because you won't GPL your code. Eventually all published software would become free.

      Microsoft has always called the GPL viral, but its designed to work more like an cancer. Other software (cells) won't be able to spawn as fast and eventually would be starved for resources and chocked out until nothing but GPL is left.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    85. Re:just.. wow by spitzak · · Score: 1

      BSD: That's as free as freedom gets, surpassing even Public Domain, which is at risk for being copyrighted or even patented by anyone who files an application.

      I'm sorry but I don't see how BSD prevents somebody from doing this more than Public Domain does. Somebody can file a patent on anything and it really does not matter what license the original thing has.

    86. Re:just.. wow by clang_jangle · · Score: 1
      No. If you use BSD code, call it your own, and patent/copyright it you are in violation of the license and in violation of copyright law. The BSD license has the same backing of copyright law as any other, and it has already stood some pretty definitive legal testing (look it up, wikitard). As for the licenses themselves, from http://www.linfo.org/bsdlicense.html :

      The only restrictions placed on users of software released under a typical BSD license are that if they redistribute such software in any form, with or without modification, they must include in the redistribution (1) the original copyright notice, (2) a list of two simple restrictions and (3) a disclaimer of liability. These restrictions can be summarized as (1) one should not claim that they wrote the software if they did not write it and (2) one should not sue the developer if the software does not function as expected or as desired. Some BSD licenses additionally include a clause that restricts the use of the name of the project (or the names of its contributors) for endorsing or promoting derivative works.

      So please stop the FUD. It has long since been debunked, I really don't understand why it remains such a common belief amongst otherwise intelligent people...

      --
      Caveat Utilitor
    87. Re:just.. wow by clang_jangle · · Score: 1

      BTW: "wikitard" is not directed at you, just at the inevitable twit posting [citation needed] as a substitute for bothering to have an education or even STFW. :)

      --
      Caveat Utilitor
    88. Re:just.. wow by dbIII · · Score: 1

      Just recharging it now you bastard :)
      Anyway, my point was that something has to be more powerful and expensive to make than an iPhone to actually run the MS mobile OS. That prices Nokia out of most of their market because dirt cheap processors are not going to be able to run something like that for a a few years. They've just handed most of the worlds market to dodgy low end Chinese phones you've never heard of which will probably look a lot like clones of existing Nokia models. Maybe that was going to happen anyway, but either way they are giving up their market and going for the much smaller top of the market where they won't be able to make much headway against the iPhone.
      Sounds to me like MS going after Apple by proxy and as a side effect (because that will not work) reducing Nokia to the point where they will either vanish or get taken over.

    89. Re:just.. wow by spitzak · · Score: 1

      I'm not saying anything is wrong with the BSD, just that I don't see how it (or the GPL or any other license) protects against patent claims.

      If somebody is going to file a patent on an idea they stole, they certainly are not going to point out where they got the idea. So nobody will see that it was originally BSD (or public domain, or whatever). Since they don't see it, it seems unlikely the license will matter.

      Open source including BSD, and public domain may help some because there may be good proof that the idea existed before the attempt to patent it was made.

    90. Re:just.. wow by Mana+Mana · · Score: 1

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

      *sigh* You are free to use the BSD licensed code, no one will stop you! Closing their source addition is a feature granted by the BSD coder/s. How are you going to tell him how to give you a gift; it's his gift.

      However, the author licensed his code with certain conditions. Amongst them attribution, (license) header inclusion in _perpetuity_. That, `I'll take that BSD code and GPL it' trope is a myth. As, per license terms, the BSD license headers must be attached and be displayable, with all end product. This issue has been hashed here before, years ago. My hero Alan Cox, I love you, babe, put his foot in his mouth (for a time) arguing the very same trope.

    91. Re: Re:just.. wow by Nursie · · Score: 1

      "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."

      But how many theoretical people get to use your proposed output is not relevant. At all.

      The GPL is a mechanism where I, the writer of your awkward component, ensure that anyone who ever gets it from anywhere, altered, adapted, binary, whatever, gets to enjoy open source. That's not true of any of the other licences.

      Don't like it, don't use it.

    92. Re:just.. wow by exomondo · · Score: 1

      Someone taking BSD code and marrying it with their own proprietary code doesn't do anything to the original code, that code is still there and free to be tinkered with and learned from.

      Not when it comes on a closed up device, with no way of running it on that device and likely not even an indication that there's even any BSD code in there.

      Same as with GPL code.

      So, I as a recipient of BSD code in binary form - I might not know it's BSD, the original project could have disappeared or gone offline, all sorts of stuff. To say it *never* goes away is simplistic.

      The GPL situation is worse, if the code disappears then the binary is pretty much useless. At least the binary can still be used in the BSD situation.

      Actually it's neither. As a consumer I want to tinker with my device.

      What do you mean by 'device'? I'm pretty sure what you want to tinker with is the proprietary code. There is no FOSS licensing issue with tinkering if you strip the software from the hardware.

      The right to ask the binary distributor for the source

      No, no-one takes that right from you, you always have that. What you want is the right to force the distributor to give you the source.

      It's not that I demand the right to use other people's code, it's that they have to play ball if they want the right to use mine.

      And you're entitled to that, but from my point of view if i release free code then people are free to use it however they wish.

      If you like to think of BSD as more altruistic as a result then that's up to you, but if you look at the software ecosystem (particularly consumer devices with embedded operating systems) you'll see that the GPL often opens up a lot of areas of cool hobby-type stuff that would have stayed closed if there was no publishing requirement for linux.

      Not really, the real 'cool hobby stuff' on consumer devices would be available if linux were under the GPLv3, which it isn't.

    93. Re:just.. wow by exomondo · · Score: 1

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

      That's why - when using the GPL - 'freedom' comes with a caveat.

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

      No, you can't deny anyone the freedom to use my BSD code.

    94. Re:just.. wow by MikeBabcock · · Score: 1

      You might want to have a look at the devices supported by CyanogenMod for example. He doesn't even cover the most devices. There has always been an issue with the ability to run the kernel on a device, often referred to as the Tivo issue. Hardware lock-out measures need to be dealt with elsewhere however, as its quite obvious they shouldn't be dealt with in software Copyright (the GPLv3 aside).

      That said, I own multiple devices that came with copies of the Linux kernel that I've patched and reinstalled. Incidentally, improvements or changes to the kernel or other GPL'd software made for these devices doesn't necessarily only apply to those devices, and the visibility of that code can help improve other use cases as well.

      "Freely you received, freely you should give."

      --
      - Michael T. Babcock (Yes, I blog)
  3. Next by smileygladhands · · Score: 1

    Next is Qt.

    1. Re:Next by Anonymous Coward · · Score: 5, Informative

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

    2. Re:Next by bmo · · Score: 1

      Someone mod parent up, plox.

      --
      BMO

    3. Re:Next by Anonymous Coward · · Score: 0

      This actually makes me respect KDE a little more... I had no idea...

      This is exactly what we need more of in the open source world, though. If some company is in charge of something, make it so that the community can keep it open source, regardless of what the company does, by contract.

    4. 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.

    5. 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."
    6. Re:Next by maxwell+demon · · Score: 1

      Not being Gnome isn't enough?

      Microsoft Windows isn't Gnome either.
      Just saying.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    7. Re:Next by Chrisq · · Score: 1

      Not being Gnome isn't enough?

      Microsoft Windows isn't Gnome either. Just saying.

      How dare you say something nice about Microsoft here!

    8. Re:Next by TheRaven64 · · Score: 1

      Microsoft Windows isn't Gnome either.

      Has anyone informed Michael de Icaza of this?

      --
      I am TheRaven on Soylent News
    9. Re:Next by calagan800xl · · Score: 2
    10. Re:Next by Hognoxious · · Score: 1

      Not really a valid comparison - Gnome and KDE aren't operating systems. Er, hang on a mo...

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    11. Re:Next by sapgau · · Score: 1

      That is a good sign indicating the longevity of open source projects vs. commercial "ventures".

      If only my boss could see the benefit of investing more on open source vs. chasing the eternal upgrade race from our vendors.

  4. 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 Anonymous Coward · · Score: 0

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

      ftfy

    3. 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
    4. Re:Why close it now? by Ukab+the+Great · · Score: 1

      So you're saying Nokia closing the Symbian source is like cutting the head off a zombie you blasted with a 12-gauge a little while ago just to make sure it's good and dead?

    5. Re:Why close it now? by Anonymous Coward · · Score: 0

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

      Don't you play WoW? It's spelled "rouge". :P

    6. Re:Why close it now? by Anonymous Coward · · Score: 0

      Too late. You can't put the genie back in the bottle. If some rogue developer cares, he'll just fork an existing free version.

    7. Re:Why close it now? by dbIII · · Score: 1

      Yes, if it revives Nokia may stay large enough to operate as their own company instead of the taken over mobile phone division of another company that can't afford to buy it at the moment. You are seeing yet another deliberate corporate wreck in progress.

    8. Re:Why close it now? by Anonymous Coward · · Score: 0

      Then didn't close it, it was never open in the first place. It was reported to be opened a few days ago. This is an update about that they didn't open it.

    9. Re:Why close it now? by TheRaven64 · · Score: 1

      It makes it harder to build a community though. I know someone who grabbed the last Apache licensed sources before they closed them, and probably other people did, but there's no central place for all of these people to communicate. That said, without at least one device maker wanting to back Symbian, it's probably dead. Minix 3 looks like it's probably the only viable microkernel for a little while.

      --
      I am TheRaven on Soylent News
    10. Re:Why close it now? by Anonymous Coward · · Score: 0

      Rule #2: The Double Tap.

    11. Re:Why close it now? by Anonymous Coward · · Score: 0

      Yup. Double-tap. It's one of the rules.

    12. Re:Why close it now? by Anonymous Coward · · Score: 0

      Yeah, it is possible to fork Symbian now but you'd need a lot of work and commitment.

      It's certainly possible to succeed at this, OpenSSH started from an ancient version of the commercial SSH just before they switched licenses. Admittedly that's a relatively small project with a top-notch team behind it.

      It's early days for Libre Office but they're clearly moving in the right direction. They already had decent developer community and they've got some commercial backing, Red Hat and Novell are paying some of those salaries I think.

      I don't know if enough people care about Symbian to do the required grunt work.

    13. Re:Why close it now? by Eunuchswear · · Score: 1

      Shit, I'm so slow I thought you were talking about the shitty touchscreen UI Nokia came up with for Symbian (one tap to select, one to open).

      Duh.

      --
      Watch this Heartland Institute video
    14. Re:Why close it now? by Anonymous Coward · · Score: 0

      Not at all, I think he meant it's like cutting the head off the last standing zombie while running out of the city, just to ensure nobody else could benefit from studying a walking dead while you're away hiding in a deserted shopping mall.

      (which i hope would've happened to be not so deserted after all)

    15. Re:Why close it now? by bill_mcgonigle · · Score: 1

      Yup, this is how you structure a merger that the regulators won't approve.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    16. Re:Why close it now? by Locutus · · Score: 1

      and you don't think Microsoft knows how to dance around regulators? Where have you been for the past 25 years?

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  5. 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?

    1. Re:I'm scared by Anonymous Coward · · Score: 0

      Unfortunately KDE is dying as a desktop. Most distros these days are using Gnome by default. It's unfortunate since the competition betters both of them, but given the QT situation it seems KDE is facing some headwinds.

    2. Re:I'm scared by Qubit · · Score: 1

      I'm started to feel like Nokia is becoming something awful

      I guess it's better to have it turn into a robot that shoots out sparks and pushes grandmothers down stairs than having it turn into Microsoft...

      --

      coding is life /* the rest is */
    3. Re:I'm scared by Anonymous Coward · · Score: 0

      For a minute I thought you were going to let slip the Terrible Secret Of Space.

    4. Re:I'm scared by Chrisq · · Score: 1

      I'm started to feel like Nokia is becoming something awful

      I guess it's better to have it turn into a robot that shoots out sparks and pushes grandmothers down stairs than having it turn into Microsoft...

      Possibly. So far "The Doctor" had failed to come and save us from Microsoft. He always turns up when killer robots push grandmothers down stairs.

    5. Re:I'm scared by ElusiveJoe · · Score: 1

      And with Gnome 3.0 release they're dying together! Seriously, what a nonsense!

    6. Re:I'm scared by Anonymous Coward · · Score: 0

      I, for one, welcome our new Gnome overlordi!

      (WHOOSH)

  6. another bad news... by Anonymous Coward · · Score: 1

    What did Microsoft with Nokia? :(

  7. Open by Archangel+Michael · · Score: 1

    Nokia Exec: "We're Open and direct"

    Slashdot BS filter: We're open, like Goatse. And direct, like flying chairs.

    Goodbye Symbian, Goodbye QT, Goodbye Nokia. Everyone start migrating now, the borg are about to swallow it all.

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    1. Re:Open by afidel · · Score: 1

      QT will be sold off for pennies on the dollar if they don't jettison it before the bankruptcy filing to try to keep their core business afloat a little longer.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    2. 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.
    3. Re:Open by wvmarle · · Score: 1

      Goodbye Symbian, Goodbye QT, Goodbye Nokia. Everyone start migrating now, the droids are about to swallow them all.

      FTFY.

    4. 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
    5. Re:Open by Jeff+DeMaagd · · Score: 1

      The problem is they've signed onto an OS that the market doesn't seem to want, at the expense of Symbian. Symbian might not have had a high profile, it seemed to be pretty successful. What is the fall-back plan? Going back to the OS they let hang for a year? I hope they're still continuing to advance Symbian, because a lot happens in a year.

  8. 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.

    1. Re:Borg assimilation in progress by Anonymous Coward · · Score: 0

      ... and?

      HP-UX is still alive and kicking.

    2. Re:Borg assimilation in progress by gtall · · Score: 1

      While I agree with the sentiment, a single case does not an induction argument make. Or co-induction, for that matter.

    3. Re:Borg assimilation in progress by Anonymous Coward · · Score: 0

      Hard to say. Nokia has been dying since then end of 2007. Look at their stock. Every other good company has come back from the crash stronger than ever, meanwhile Nokia has been steadily sinking the whole time.

      iPhone and mostly Android killed Nokia. Android was unveiled at the end of 2007. They should have embraced it early when they still had a chance.

      All this did was provide an opportunistic for Microsoft to put the nails in the coffin at a good price. I wouldn't say it was Microsoft that did them in though. They made their own mistakes a few years ago.

  9. 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 Anonymous Coward · · Score: 1

      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.

    2. 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
  10. Seriously? by BlueParrot · · Score: 1

    Are they TRYING to lose relevance? This is just bound to drive developers towards android, and what exactly would the benefit be? It's not as if they're in a position to press clients into paying license fees since that would just drive them away.

    1. 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.
    2. 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.

  11. 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 Anonymous Coward · · Score: 0

      It would not have failed for that reason alone (many open source projects are commercial quality) and who says that commercial backers are not an option with open source projects?

    3. 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?

    4. Re:Stick a Fork in it, its done! by Kjella · · Score: 1

      Debian seems to be doing quite well, despite not being very commercial. Plus there's quite a few non-profit foundations like Apache, Mozilla, KDE, Gnome, FSF etc. that don't as such exist to become the next Red Hat, but there's no doubt raising enough funds to say it is your day job is a huge advantage. If it's just your hobby outside of work/studies then it takes a lot less to make you give it up. Things like crunch time at work, exam time, spending time with a girlfriend or just life in general taking priority. Besides, people don't come home from one work day and regularly pull another 8 hour shift. Not if they want to live to see 30 anyway. I guess what I wanted to say is I don't think it's "commercial" in the sense of "turning a huge profit" that does it, but as in "I can work on this all day and it pays my bills". But then again, turning a profit is a good way of having money to pay salaries...

      --
      Live today, because you never know what tomorrow brings
    5. Re:Stick a Fork in it, its done! by dlgeek · · Score: 1

      Debian

    6. Re:Stick a Fork in it, its done! by Eskarel · · Score: 1

      Debian isn't massive-scale. It might have a lot of users, but the amount of code which is purely debian is actually fairly small. Coding Symbian would mean maintaining the entire OS, and perhaps more importantly it would mean making the entire OS not suck which Nokia couldn't do with millions of dollars.

    7. Re:Stick a Fork in it, its done! by TheRaven64 · · Score: 1

      Debian seems to be doing quite well, despite not being very commercial

      How much code is Debian responsible for? The kernel comes from Linux (of GNU or FreeBSD, depending on the variant), the userland from GNU, the toolchain from GNU, the GUI from X.org, the apps from other third parties. About the only thing that's Debian-original is apt, and that has a lot of non-Debian contributors these days. Debian packages software fairly competently, but it isn't a shining example of development.

      --
      I am TheRaven on Soylent News
    8. Re:Stick a Fork in it, its done! by old+man+moss · · Score: 1

      The code that was released under the EPL by the Symbian Foundation is still available from the legal remains of the Symbian Foundation if you want it. Nokia have simply said that all further developments by them and their partners will not be released under that license.

      --
      rt
    9. Re:Stick a Fork in it, its done! by evilviper · · Score: 1

      OpenBSD and related projects (eg OpenSSH) certainly aren't.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  12. Unleash the Fury by Anonymous Coward · · Score: 0

    of the Nerd Rage.

    1. Re:Unleash the Fury by fuzzyfuzzyfungus · · Score: 1

      This is Symbian we are talking about. Not interesting enough to stir nerd rage; but not dead enough to stir nerd nostalgia. Try back in a decade, maybe, and there might be a tiny group of hardcore Symbian retrophone enthusiasts, like the Amiga guys, pulling impressive but irrelevant stunts to keep their favorite OS running on available hardware....

    2. Re:Unleash the Fury by BasilBrush · · Score: 1

      My nerd nostalgia is for EPOC32. The original name of the OS whilst it was used for it's original purpose of powering Psion 5 PDAs. In many ways a beautiful OS... before Nokia started fucking it up.

    3. Re:Unleash the Fury by TheRaven64 · · Score: 1

      It's still a beautiful OS. EXA2 is a much nicer kernel than EPOC32. The problem is the horrible userland crap piled on top.

      --
      I am TheRaven on Soylent News
    4. Re:Unleash the Fury by BasilBrush · · Score: 1

      I think you mean EKA2 is much nicer than EKA1. "Epoc Kernel Architecture". Epoc32 was the whole OS, not just the kernel. But yes, I agree, the Symbian kernel improved over time. Userland got worse.

  13. 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?"

    1. Re:Worked at a Symbian-using Japanese Company by tftp · · Score: 1

      Her response when I told her about the iPhone 2g? "Why would anyone use that? Won't it get finger prints all over it?"

      Believe it or not, this is one of my several reasons to not use any of those finger-oriented touch screen devices. I guess different people perceive it differently, but for me it is disgusting to look through fingerprint smudges.

    2. Re:Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 0

      You can buy a scratch protector that is fingerprint resistant. It's like 5 bucks for 3 of them. I have no smudges or fingerprints on mine and I use it every day. They sell them at the Apple store.

    3. Re:Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 0

      i don't like fingerprint smudges either, but is it that hard to wipe the screen every now and then? I mean it's not like the smudges are permanent stains

    4. Re:Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 0

      All things aside - the iPhone is a huge huge hit in Japan. It's completely overturning previous ideas about phones here. Docomo, for example, has an entire price level set aside for "Smart phones". When compared to the "innovative" Apple, Fujitsu is just another brand that competes on its phone case and colours.

      While your observation is correct, it is too conservative. Trying new form factors & ideas at the same time is necessary when you want to keep at the spear's edge. After years of barely-profitable "just past the gate" efforts, they now are merging their mobile division with Hitachi (another anonymous Galapagos handset builder). I'm willing to bet that the merger of the two poorly managed mobile sections will result in twice the mediocrity.

      There were some interesting things that they did last year, but from my understanding, no one bought them. Could you blame them? Fujitsu has some of the worst software interfaces ever built. (Japan also has some pretty awful programmers, but that's another story...)

    5. Re:Worked at a Symbian-using Japanese Company by tftp · · Score: 1

      but is it that hard to wipe the screen every now and then?

      I don't want to pay several hundred dollars for the privilege to carry a cloth and wipe the screen like a cleanliness-obsessed mental patient. If the device is designed to be dirty then I don't want it. Hardly any loss to me, by the way - I have little use for such slow and small devices (that's where my other 17 reasons for not using them are coming from.)

    6. Re:Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 0

      Parent here: Hope you don't have a pair of glasses :-)

    7. Re:Worked at a Symbian-using Japanese Company by indiechild · · Score: 1

      The iPhone 4 is much better now in this regard, the oleophobic coating actually works. I rarely notice my fingerprints on the screen.

      My original iPad and original iPhone 1st gen are pretty horrible with fingerprint smudges constantly visible. I've been told the iPad 2 is still the same in this regard.

    8. Re:Worked at a Symbian-using Japanese Company by mcvos · · Score: 1

      Interesting point. Would touch screens be more popular among people with glasses? It wouldn't even surprise me all that much.

    9. Re:Worked at a Symbian-using Japanese Company by whisking · · Score: 1

      I think many people carry some cloth with them most of the time, I think it could even be majority. In fact, I am wearing pants right now, even though I am alone at the office!

    10. Re:Worked at a Symbian-using Japanese Company by m50d · · Score: 1

      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?"

      And in terms of the Japanese culture, she's probably right. Are iPhones at all popular over there?

      --
      I am trolling
    11. Re:Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 0

      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?"

      She had a point. I wonder how many people already died of horrible infectuous diseases because they touched an iPad in a shop.

    12. Re:Worked at a Symbian-using Japanese Company by Jeppe+Salvesen · · Score: 1

      What the hell? Are you a naturist or something? I wipe my Galaxy S on my pants 98% of the time. I've got no problem finding a suitable wiping surface - I've yet to find a fabric that scratches the screen. Every once in a very long while (once a month?), I'll clean the screen with something that solves grease. Keeping your device clean is really no problem.

      --

      Stop the brainwash

    13. Re:Worked at a Symbian-using Japanese Company by raju1kabir · · Score: 1

      And in terms of the Japanese culture, she's probably right. Are iPhones at all popular over there?

      It's the number one selling smartphone in Japan, by a significant margin. So in that sense, yes.

      On the other hand, smartphones aren't that big in Japan in general. Most people use devices that are somewhat shy of that level of complexity. They do a few things really well but aren't general-purpose computing devices.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    14. Re:Worked at a Symbian-using Japanese Company by Rich0 · · Score: 1

      the idea of building a phone for the gigantic foreign market never hit them, apparently.

      That is pretty typical Japanese culture. Foreign markets are usually of secondary concern to them. The only reason they were as successful as they were was that American manufacturers were SO reluctant to change that even an unenthusiastic foreign corporation could clean house.

      Why would anyone use that? Won't it get finger prints all over it?

      I know somebody who works in Pharmaceuticals and they had to buy special equipment to make pills for the Japanese market. To be accepted by a Japanese consumer, a pill needs to be perfectly white without any sign of blemish or visible imperfection. While this is a general concern in any manufacturing process, an American won't ask their doctor to prescribe something different if they find one pill with a ding or a slight discoloration in the bottle.

    15. Re:Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 0

      Maybe you should wash your hands once in a while.

    16. Re:Worked at a Symbian-using Japanese Company by Anonymous Coward · · Score: 0

      thats what i thought too until i got one. its a non issue if the device has gorilla glass on it, like most modern devices do. the smudges just wipe right off by sliding your finger over them.
      http://www.corninggorillaglass.com/

    17. Re:Worked at a Symbian-using Japanese Company by Eunuchswear · · Score: 1

      People who wear glasses don't touch the lenses. If I get a finger smudge on my glasses I wash them at the earliest opportunity.

      As for finger smudges on the phone, they come off when I stick it in my pocket.

      (The dust/lint, now that's a problem).

      --
      Watch this Heartland Institute video
    18. Re:Worked at a Symbian-using Japanese Company by malice · · Score: 1

      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?"

      ...but cell phones in Japan are so advanced, they are 5 years ahead of the iPhone, it'll never sell there.

      Oh wait...

  14. 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.

    1. Re:Good move! by BobboBrown · · Score: 1

      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.

      So you wrote code with only zeroes?

  15. Oblig Simpsons Quote by Anonymous Coward · · Score: 0

    I love when sentences can be ambiguously changed later by redefining the meaning of words...

    Hutz: All right gentleman. I will take your case. But I will require a thousand dollar retainer.
    Bart: A thousand dollars. But your ad says "no money down".
    Hutz: Oh, they got this all screwed up. [corrects ad with felt-marker]
    Bart: So you don't work on a contingency basis?
    Hutz: No, money down. Oops, I shouldn't have the Bar Association logo here either. [Hutz eats ad]

    1. Re:Oblig Simpsons Quote by Anonymous Coward · · Score: 0

      I love when sentences can be ambiguously changed later by redefining the meaning of words...

      You have it backwards...when you see a sign on the window of a shop that says 'we are open' that doesn't mean 'open source'.

    2. Re:Oblig Simpsons Quote by Anonymous Coward · · Score: 0

      oh... should have told me that before I liberated all those CDs.

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

    ...dead.

    --
    If you want news from today, you have to come back tomorrow.
    1. Re:Nokia Confirms Symbian Is... by Anonymous Coward · · Score: 0

      Well, he's...he's, ah...probably pining for the lakes.

  17. Yes! by Greyfox · · Score: 1

    What I get from this is that they've seen and fear Android's success! You see, technical support is one of the largest expenses in maintaining your own platform, and they've cleverly deduced that if you don't have customers, you don't have to pay for technical support! They plan to ride this strategy all the way to the top of the heap!

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:Yes! by Compaqt · · Score: 1

      Nokia's strategy: lose on every sale, and make it up on volume. Sad to see a storied, century-old company go like this.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
  18. 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.

    1. Re:Open Is As Open Does by Anonymous Coward · · Score: 0

      Just one question:
      why would they spend 39$B on RIM if they can make "partnership" like one they have with Nokia now. They just wait for RIM to implode and pick IP for small change

  19. So much for open. And direct? by Opportunist · · Score: 1

    So "open" is not for open source but for "open for business".

    And I guess "direct" is not for, well, "direct", but rather for "we just act as if we're doing something useful", as in "directing a movie". Or is direct now the opposite of erect, i.e. the opposite of upping something up?

    It's all in the definition. Not the delivery.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  20. 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 Anonymous Coward · · Score: 0

      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.

    3. Re:Amazed by Anonymous Coward · · Score: 0

      For many fins Bill Gates is the real Jesus and Microsoft his gift to us all.

      I believe that the majority of the finnish elite believes that the holy MS is going to catapult Nokia
      to heaven.

      Microsoft had moles+religious fanatics inside Nokia before Elop walked in.

    4. 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.

    5. 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.

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

      Somebody gave somebody lots of money.

    7. Re:Amazed by DrXym · · Score: 1
      Nokia was blindsided by Android.

      The weird part is why they didn't go with it in the end. They could have skinned Android, dropped in a Symbian runtime so their apps still worked, customised the UI anyway they felt, dumped in an Ovi store and married the lot to their hardware. Now they have to take the Windows Phone OS and like it. I'm sure MS will give them token ways to modify the experience, but it won't be anything like what they could have done.

    8. Re:Amazed by sp765uubox · · Score: 1

      I still get amused when people call Elop a "Trojan" as if he somehow snuck in and took over the company without anyone noticing. I mean, think what you want about the MS deal, but the reality is that the board installed him to do something exactly like this. At the request of major shareholders who were tired of watching their investment disintegrate under current Nokia direction. That "shareholder revolution" we heard about? It was a hoax. That was one bored random dude with no investment in Nokia at all. Wake up people, the shareholder's aren't going to revolt and remove Elop. Installing Elop WAS the shareholder revolution.

    9. Re:Amazed by sp765uubox · · Score: 1

      I think they didn't go with Android because they were terrified of becoming "just another android maker" in what is already a fairly bewildering device market. WP7 is just gestating and they are the only device maker that now has the right to customize it so they actually have a bit of room to differentiate themselves or so the logic goes. I don't claim to know whether this is ultimately a good decision.

    10. Re:Amazed by marcosdumay · · Score: 1

      The shareholders are probably quite busy trying to dump their shares, the don't have time to dump the CEO.

    11. Re:Amazed by fritsd · · Score: 1

      Yes, this is what I read here:
      http://www.bloomberg.com/news/2010-07-15/nokia-board-faces-calls-for-management-change-after-77-billion-lost-value.html
      Basically, the large shareholders were unhappy in 2010 about the display of insecurity in spreading the R&D over Maemo, Symbian and then Meego, and jealous of the relatively larger successes of Apple and RIM (quote from the article: "Investors say it's not enough" instead of something like "researchers say it's not enough").
      Also they apparently wanted a CEO from the USA instead of another boring Finn.
      And now, the've got what they wanted: a CEO from North America who manages by the old tune of "It's a panic situation! Something must be done!!!!11! This is something, therefore it must be done! No time to think^Hlose!"
      (Sidenote: talking about that management style, I'm glaring at you, Jan Peter Balkenende! Please become CEO of Microsoft. Thank you.)

      --
      To be, or not to be: isn't that quite logical, Slashdot Beta?
    12. Re:Amazed by dbIII · · Score: 1

      I know for one thing over here (Australia) when Sol Trujillo was wrecking Telstra both sides of politics would have been very happy to catch him molesting kids or something so they could throw him out of the country. Nokia is a bigger chunk of their country and they have far more of their economy at stake.

    13. Re:Amazed by sapgau · · Score: 1

      +1

    14. Re:Amazed by rtfa-troll · · Score: 1

      Microsoft is dying (damnit BSD Trolls :-). You can't see it now, but you can see it in the intertia. Everybody knows that if you partner with them successfully as did IBM, Novell, Borland, the anti-virus companies, Netscape and so on then eventually Microsoft will get interested in your business and try to take it from you. Sensible developers try to keep a distance, continually thinking about how to move to other platforms. At the same time all of their new products (Zune, Azure, WP6, WP7, Kindle etc.) fail to get real traction. It is not an accident that Apple has a higher valuation; anyone can see that Microsoft is disfunctional.

      There are lots of institutional investors with vast amounts of shares in both Microsoft and Nokia. I think that a bunch of the have decided that Nokia is worth sacrificing in an attempt to save Microsoft. They figure that it might not work, but if it does they will protect a much bigger investmen.

      I'm guessing these companies made it "worth while" for the senior management at Nokia to bring in an MS guy.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  21. Uh yeah, OK. by Junior+J.+Junior+III · · Score: 1

    Fuck you, Nokia. You're rapidly falling behind and becoming irrelevant. Your handset hardware is pretty nice, but the software is sorely lacking. You're very last decade at this point.

    --
    You see? You see? Your stupid minds! Stupid! Stupid!
  22. Last Open Version by rdnetto · · Score: 1

    Does anyone know where I could get a copy of the last version that was actually open? Even if it's out of date, it would really useful as a starting point for writing emulators and he like.

    --
    Most human behaviour can be explained in terms of identity.
    1. Re:Last Open Version by molukki · · Score: 1

      It was available from a Symbian Foundation FTP site until March 31st last week. No idea if they are offering it anymore at all.
      Luckily I have the whole shebang downloaded and stored somewhere on a loose hard disk.

    2. Re:Last Open Version by rdnetto · · Score: 1

      Would you be able to put them online as a torrent or something?

      --
      Most human behaviour can be explained in terms of identity.
    3. Re:Last Open Version by molukki · · Score: 1

      Probably yes. I'll try to find the HDD and create torrents next week.

    4. Re:Last Open Version by rdnetto · · Score: 1

      Thanks. Please post a link here when you do.

      --
      Most human behaviour can be explained in terms of identity.
  23. End of a failed experiment, nobody loses by hkultala · · Score: 1

    When nokia deciced to open source Symbian, they did not understand the ways how open source software/development model works.
    You cannot take a closed-source code and think that when you open the source, suddently thousands of other people will come to help you and do your work for you.

    The amount of people who actually downloaded the symbian os source code and succesfully compiled it themselves outside Nokia and some other big phone manufacturers can propably be calculated with fingers of one hand.

    SymbianOS was piece of terribly written code that used very strange coding practices, and getting it to compile was quite hard. By just giving this kind of code to public does not create any kind of "open source momentum". No people are interested in contributing to it when they cannot get any benefit from their changes, and when making those changes is so hard.

    So, in the end, nobody loses when the source is closed.

  24. And thus, a chapter of history closeth.. by cheros · · Score: 1

    How sure are we that current Nokia leadership doesn't have shares in other phone manufacturers? As fas as I can see there isn't much else left to screw up now..

    --
    Insert .sig here. Send no money now. Owner may sue, contents will settle. Batteries not included.
  25. nothing to do with the Microsoft deal by doperative · · Score: 2

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

  26. no one forked it? by dwater · · Score: 1

    I don't understand....sure, Nokia can close whatever it chooses to call 'Symbian'...but it was open in the real sense so anyone who cared could have copied the code and forked it then. It seems no body (esp. from the US and/or /.) cared to do that, so why is anyone bothered what Nokia decide to do with their copy of the code?

    --
    Max.
  27. I wonder if there is more to it by Kupfernigk · · Score: 1
    This has been going on for some time. For instance, 2 of the 3 conference chairs at MUM2009 were:
    • Natasa Milic-Frayling, Microsoft Research Cambridge, UK
    • Jonna Häkkilä, Nokia Research Center Tampere, Finland

    I suspect that a significant part of Nokia has been working for this, and for a very obvious reason; career insurance. Symbian had limited life, Maemo/Meego offered limited career scope. A commitment to Microsoft meant that Nokia engineers and managers had things on their CVs that offered prospects outside Nokia. The Microsoft deal could be a vote of no confidence in the long term future of the Finnish economy, and given the way that phone components are almost entirely made in the Far East, and applications generally made in the Anglophone world or Western Europe, they might be right.

    --
    From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
  28. Does anyone have a source tarball? by Anonymous Coward · · Score: 0

    I'm sure someone downloaded the source code under the EPL. Would it be possible to post the link for an archive, more for historical purposes than for actual development?

    1. Re:Does anyone have a source tarball? by Anonymous Coward · · Score: 0
  29. Yup. by jonr · · Score: 1

    And not a single fuck was given.

  30. look who made the statement by crimperman · · Score: 1

    This is in no way surprising but... the statement was made on the Symbian Nokia blog. Until 31 March the posts there were made by their HEad of Open Source including one on 31 march saying the source code was available and they'll be uploading the rest in coming days.

    The "oh we didn't mean that kind of open" post was made by "admin" and has no signature declaring what dept "admin" is in. So it appears that this is not a decision the Open Source team were either aware of or perhaps happy with? I'm just guessing here of course but I think the fact that this latest statement doe snot specifically come from the open source team speaks volumes.

  31. And they said... by PenquinCoder · · Score: 1

    nothing good would come from Nokia and Microsoft teaming up. When Nokia 'open-sourced' Symbian, they expected a large following of open-source developers to code their flagship mobile OS. It didn't happen; so now their running back behind closed doors like a whiny little kid taking back their toy. Hint: Nokia, it takes more than saying your code is open-source, for people to want to actively code it. For starters, how about making it even a fraction as easy or possible to compile as some other OS kernel.

  32. I told this before by unity100 · · Score: 1

    ANYthing that can be closed at the whim of a private person or party, is NOT open. 'open at whim', 'temporarily open' are more appropriate terms for these.

  33. That's why they called it "OVI" by funky_vibes · · Score: 1

    That's why they called it "OVI" (door in finnish)
    It's easy to shut...

  34. My new idea by david_thornley · · Score: 1

    That Slashdot pay a large bounty for the head of anybody who starts a Slashdot argument on whether BSD or GPL is freer. Other body parts are optional.

    --
    "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  35. Ironic isn't it by Anonymous Coward · · Score: 0

    Wasn't it Bill Gates who described open source as "virus like" ? We now know that "virus like" applies to Micro$oft and their (ex-)employees

  36. OMG! Panic! by Kamiza+Ikioi · · Score: 1

    Hold crap! What are we going to do now? Without open Symbian, whatever will we do! Will Nokia's strangle hold on smart phones never end! Oh, the humanity!

    http://thenextweb.com/location/2011/02/08/symbian%E2%80%99s-huge-market-share-looks-to-be-in-play/

    --
    I8-D
  37. Very Sad by omb · · Score: 1

    Symbian was ALLWAYS a bad platform, which got little traction outside Nokia, and some of the technical decisions eg "Symbian Signed" were brain dead marketing ideas that made the platform even more hostile. Ie if Nokia didn't do it you could not have it, even on your own phone, period.

    So Symbian spoilt Nokia's high end while the margins on the low end, simple phone eg N3110, 5 days battery life were eroded to nothing. Nothing Nokia has done, at the high end has worked and they have destroyed all confidence that they know how to build a smart-phone. I predict WP7 will be a disaster and will do neither Nokia or M$ any good.

    Nokia had the money to make QT+mego a success, but none of the drive, immagination or technical management to realize sucess.

    When the M$ adventure is seen to flop they will be done. Very Sad.

  38. Nokia trying to commit suicide by Anonymous Coward · · Score: 0

    QT propably next too. I can't help myself thinking, this must be intentional.

    CEO eLobster is either painfully trying to make Nokia commit suicide by biting itself to tongue or driving the stock price down for MSFT merger.

  39. Just imagine. by Colin+Smith · · Score: 1

    Instead of the Zune, you'll have the 'The Microsoft Nokia (tm)' smartphone.

    Lets see.. How likely is it that Nokia name will be reduced to a model of phone?
    http://www.google.com/finance?client=ob&q=NYSE:NOK

    oops:
    Nokia Debt Rating Lowered One Step by Moodyâ(TM)s
    HTC Passes Nokia in Market Cap

    Fuck this is depressing. I was really hoping for a Meego box. Oh well.

    --
    Deleted
  40. Finnish proverb for this situation by Anonymous Coward · · Score: 0

    There's an old Finnish saying that can be used when complaining how someone gave something and then changed his mind and took it back.
      "Ottaja ja antaja, kissan paskan kantaja"

    English translation with similar rhymes could be: "Giver, taker, cat poo baker".

  41. Yes on sourceforge. by krischik · · Score: 1

    There is a copy on sourceforge but no developers to improve on it.