Slashdot Mirror


IBM Offers to Help Sun Open Up Java

dave writes "ESR has opened the issue of pressuring Sun to open source Java, and today IBM throws in their own commitment toward this end. IBM has published an open letter to Sun, proposing that the two companies collaborate on an independent project to open source Java, saying that IBM is ready to provide technical resources and code for the open source Java implementation while Sun provides the open source community with Sun materials, including Java specifications, tests and code."

6 of 475 comments (clear)

  1. Licensing issues by MAXOMENOS · · Score: 5, Interesting

    Q: What's to stop Sun and IBM from open-sourcing the JDKs they have now? A: Third-party IP. Odds are, both Sun's and IBM's JDKs are chock full of third-party IP. Even the stuff that IBM implements in a "clean room way" probably contains IP that IBM licensed from somebody else. One could interpret IBM's gesture as offering to produce parts of the JDK that are free from IP encumbrances.

  2. Re:Doubtful... by Frymaster · · Score: 5, Interesting
    I haven't seen Sun do anything that leads me to believe they are really for open systems.

    then perhaps you should take a look at experimentalstuff.com - sun's site for experimental code. lots of it is opensource including an entire operating system (chorus os).

    looks like a committment to opensource to me.

  3. Re:How nice of IBM.. by d00ber · · Score: 5, Interesting

    IBM put JFS the AIX journaling filesystem into Linux. They might well respond by saying yes. I do admit that given IBMs long history of tweaking SUN (Eclipse anyone?) that this offer by IBM might not be taken that well. OTOH Sun has never seemed that hell bent on monetizing Java - the licensing and conformance testing fees probably don't begin to cover development costs.

    They say are trying to build a community around Java and it seems to me that given those two points Sun really should release Java to the open source community.

    I think this really would give Java a HUGE boost over .NOT.

    Besides, JBoss and Linux distros make money on packaging and supporting Free but hugely complex systems.

  4. Open Source dangers... by brasten · · Score: 5, Interesting

    McNealy addressed this issue year or so ago...

    The problem they're afraid of is Microsoft embracing & extending Java. The ability that Sun had to sue Microsoft and force them to cease their modifications would no longer exist.

    Now imagine Bill Gates at home in his Medina mansion.. (only 10 minutes away from here actually... sad...). Everywhere he tries to push .NET and his vision, Java's there. Java's beating him, or right behind him, on almost every front, and for the better part of the last few years, he's been unable to combat this enemy with any major success. Now imagine someone hands him the source code and tells him he can fork it however it wants. What would he do?

    I don't know. And for the time being, I'm fine not knowing...

  5. Re:How nice of IBM.. by Coz · · Score: 5, Interesting

    Brav-o. Good summary. One little thing - if Sun open-sources their own code, it's not duplicating the API - it's releasing it. Now, if there's IP in that code that's locked up somewhere, or licensed somehow, that's a problem - one that IBM should be able to help solve, given their library of IP rights.

    If I were at Sun, one of my concerns would be which of their development projects to open, and when. "Java" isn't just Java 2 Standard Edition - the Enterprise Edition and Mobile/Wireless Edition have lives of their own; then there's (still) Jini and all their XML stuff. Sun is sinking cash into lots of different efforts, trying to establish Java in market niches (like mobile phones) and building in tool support, documentation, etc. Throwing the doors open and letting the world at their code base may not be the smartest thing at the moment (esp. if there's licensed IP in there somewhere that they need to go negotiate to open, or remove).

    I'd like to see them phase in open-source. Give 'em six months or so for the 3 major "platforms", including all the java.* and javax.* packages, then another six months for the com.sun.* packages - with an expectation that other players would start working on them immediately. After that, every new thing they do should be opened no later than beta... and the JCP should allow participants to collaborate on implementations at the source-code level, so JCP members could work in semi-privacy until the code got fully opened at their beta release.

    But that's just an idea....

    --
    I love vegetarians - some of my favorite foods are vegetarians.
  6. Re:How nice of IBM.. by Anonymous Coward · · Score: 5, Interesting

    You're almost right.

    Not "any monkey" can write a VM. They're non-trivial (just ask the Kaffe folks), and IBM has several irons in the fire. As well as licensing Sun's VM (and improving it vastly for their customers) they also have their own VM under development, entirely free of Sun IP.

    On the issue of class libraries, you're also nearly right. Swing would be hard work, and pointless. There's a reason that eclipse doesn't use Swing... IBM isn't interested in it - it sucks.

    IBM also has their own set of class libraries under development - entirely free of Sun IP.

    So, in my opinion, this is just a huge red herring. IBM has enough projects under heavy development to release a completely open-source VM and set of class libraries within 18 months if they want to.

    Personally, I think it's going to happen, and this is them tapping on Sun's window going "if you don't do it, we will, and we'll do it without using your IP".