Slashdot Mirror


Sun backs off Open Java Plan

Josh Baugher wrote a line to point us over to this Wired article. Sun has backed off the original plan to have Java submitted as an open standard to the Internation Standards Organization. Sun and the ISO have been arguing over things, because the ISO is a bit less then happy with having one company retain control of the technology.

11 of 86 comments (clear)

  1. Re:HA! This is funny. . . by Aaron+M.+Renn · · Score: 2

    Eric, how many patents encumber MP3 and the MPEG-4 standard? Is there a reference on the web where I could look them up?

    BTW: I consider the ISO's policy of allowing patented standards simply awful. The IETF will accept nothing as an internet standard that is encumbered by patents. The ISO working groups are dominated by companies and works for their benefit. There is no point in a "standard" that you are not free to implement unless you pay royalties. That's just my opinion, of course.

  2. Re:Java is open source by Aaron+M.+Renn · · Score: 2

    I think both Kaffe and Japhar+Classpath are committed to providing a fully compatible Java implementation. This will not extend to replicating JDK bugs possibly, but I think all of those projects are committed to the Java wora concept.


  3. ISO changed PAS rules... by Dawn+Keyhotie · · Score: 5
    Microsoft couldn't kill Sun's ISO application outright, but they did have enough leverage to get the ISO committee to change the rules that apply to Publicly Available Specification submitter, or PAS, organizations. Initially, ISO created the PAS program so that hot new technology could be quickly standardized and submitted to ISO by the creator of the technology, instead of by the decades of committee wrangling that normally accompanies an international standardization effort. Witness C, C++, Fortran, etc. As a PAS participant, a company would drive the development of the new standard, with oversight and approval of the ISO subcommittee for that standard. While others would be free to implement their own compatible version of the PAS initiated standard, only the PAS submitter would be able to initiate changes in the standard, with the committee's approval of course.

    Microsoft applied pressure behind the scenes and got ISO to change the rules for PAS submitters so that once the technology had been submitted and approved, all control would be handed over to the ISO subcommittee. Sun, of course, has said from the beginning that they would always maintain control of Java(TM) and would vigorously defend it against all who would try to wrest control from them. As indeed they have.

    And now that ISO has changed the PAS rules to force Sun to either relinquish control of Java(TM), or drop the ISO standardization effort, Sun has chosen the path that is consistent with their stated goals of retaining control of the evolution of Java(TM), one of the most important new technologies of the Internet era. Bye bye, ISO.

    I agree with Sun's position, especially in light of the fact that the rules were changed out from under them in a sneaky back-room deal.

    Java(TM) will continue to evolve. Sun does need to a better job of public relations, and to help more people implement Java(TM) for their platforms of choice. While I agree that a GPL'd implementation would be best, I don't expect Sun to just throw in the towel and give up its control. They are way too 'corporate' for that. From a Sun shareholders perspective, that would be the equivalent of flushing money down the tubes. And lots of it.

    --
    "The only good windmill is a tilted windmill."
    1. Re:ISO changed PAS rules... by L1zard_K1n6 · · Score: 2

      The PAS rules are ridiculous.

      Sun knows Java is ready to be opened up - they simply want to keep their hands on it.

      If in fact Sun does intend to make dramatic changes to the language, in which case it might be justifiable to keep tight control, then this is a warning sign to developers to keep away from Java until the dust settles. If the language is not going to change significantly, then developers should be suspicious of Sun's motivations.

      In either case, developers should steer very clear of Java for the forseeable future.

  4. More Information... by pspeed · · Score: 2

    For more information, check here:

    http://www.zdnet.co.uk/news/1999/1 6/ns-7955.html

    Apparently, Sun is upset because the rules were changed on them. See if you can guess who lobbied for these changes. They have not given up on standards processes in general; They've just given up on MS-ISO.

    --
    Edu. sig-line: Choose rhymes with lose. Chose rhymes with goes. Loose rhymes with goose.
    Comparing? THEN use THAN.
  5. Re:HA! This is funny. . . by Eric_Scheirer · · Score: 3
    There's a difference between allowing a single company to control the standard and allowing patents into the standard. Contrary to popular opinion, Fraunhofer is not the only patent-holder on MP3 technology -- they participated in the MPEG process with a number of other companies. They have just been the most aggressive in pursuing infringers. And FhG doesn't control the *direction* of the standard -- only MPEG does that, and it's according to MPEG's normal working rules.

    The situation was much different with Java. Sun wanted simultaneously to have Java be an International Standard, but also reserve the right to make unilateral changes to the technology if they decided that it was in their interest to do so.

    The difference is clear for MP3 -- no individual company controls the MP3 standard; if revisions need to be made, this is decided by MPEG as a whole, not by Fraunhofer or any other individual company. Sun could not accept letting the other ISO members share in the role of deciding the progression of Java. This is their right, as they own the Java technology, but then the technology can't be an International Standard.

    -- Eric Scheirer
    Editor, ISO 14496-3 (MPEG-4 Audio)

  6. Cutting off your nose to spite your face by TWR · · Score: 2
    There are just way too many people here who say they will never use Java as long as it is under Sun's control.

    That's a completely self-defeating attitude. Java is a great language/platform/whatever. Development times are greatly reduced, stupid pointer bugs are a thing of the past, and the class libraries are pretty robust. I could also chant "cross-platform" until I'm blue in the face, but that's not the most important Java feature, IMHO. Making life easier for developers produces better software. The time I used to spend tracking down errant pointers is now spent improving my code. It's that simple.

    If you don't want to use a superior tool because you don't like the fact that it's not an officially sanctioned standard, you're making a serious mistake. If you're a professional, your competitors will just use the better tool and beat you. If you hack for the love of code, not using the most elegant tool pretty much defeats the point of writing elegant code. Use the best tool for the job; being a platform/language bigot is boring.

    -jon

    Java hacker since 1996

    --

    Remember Amalek.

    1. Re:Cutting off your nose to spite your face by TWR · · Score: 2
      Except that you would make an ass of yourself. Even Sun has toned down the cross-platform rhetoric now that they realize it cannot be made a reality.

      I'm reasonably sure that I've said this before on /., but it bears repeating. I've written a multi-threaded messaging and middleware server which runs _without modification to any source or binary_ on Mac OS, Win32, Solaris, HP-UX, AS/400, and AIX. This was about one year ago, and Java has grown a bit in the past year. Name the other languages, then or now, which allow you to do the same thing.

      I'm currently writing a neat little program to help me organize fantasy baseball stats. I develop it at home on my Mac, and I run it unmodified on my NT box at work. The size of the Java executable (jar file): 60K. This program is sucking data down from Yahoo, organizing it, parsing date and time fields, saving files, and displaying data on-screen with Swing widgets. It's non-trivial. And it just works, cross-platform.

      It's pretty clear that you don't know what you are talking about when it comes to Java and it's cross-platform capabilities.

      All of this talk isn't just hot air- look at the mess VB has become under MS's closed control. Java will certainly go the same way as Sun morphs it into something more useful with Jini or whatever their latest plan is.

      Funny you should mention VB. Java is turning into cross-platform VB. For building in-house apps, Java w/Swing is a great tool, with multiple vendors supplying builder environments. Enterprise Java Beans are a very cool server-side technology, with support from about a dozen vendors.

      The key difference between Java and VB is that high-quality Java tools and environments are available from multiple vendors. The same is not true of VB. Java code can migrate and keep you from being locked into a particular vendor. The complete spec for the language and JVM are freely downloadable. Just because Sun OWNS Java doesn't mean that there isn't plenty of documentation out there.

      Sun has franchised Java to multiple vendors. Those franchisees get to call their product Java. If you want to clean-room a Java clone, it's certainly possible, given the info that Sun has released. Do you refuse to eat at McDonald's because they don't let anyone who makes a hamburger put up the Golden Arches?

      -jon

      --

      Remember Amalek.

  7. Give it some time to mature before freezing it. by brad.hill · · Score: 2
    I'm no expert on the history of programming languages, but it seems to me that one of the big advantages of Java is that it doesn't carry around a lot of baggage; baggage from C or even it's own baggage.

    Java is still a young language, and even the best designs have problems that become apparent with use. I'd give Java some time to mature under the direction of an entity more nimble than the ISO. Rigorously enforced standards are most important for constraining the future of languages with a lot of extant code (C, Fortran). A young language should be able to make some deprecations and fix some mistakes because the tradeoff of making some amount of JDK1.0 or even 1.1 code incompatible is small compared to the importance of getting it right for the long run.

  8. Java : R.I.P. by L1zard_K1n6 · · Score: 2

    Any notion I had of adopting Java for any project is hereby dropped.

    Sun is demonstrating that they are the Microsoft of the Unix world - they will manipulate Java in arbitrary ways to forward their goals, regardless of whether the users see any benefit.

    Beware closed languages. This lesson has been learned well by developers who have been bitten by closed 4GL languages in the past, for example (yes, I know Java is not a 4GL).

    Java could have ranked up there with perl as one of the great languages of the 90's, but now, at least in my mind, it has been resigned to bit bucket with all of the other closed go-nowhere languages that clutter the development landscape.

  9. Sun's full of it: read the ISO mail yourself by ljs127 · · Score: 2

    The discussions of the Java Standards Group (JTC 1 SC22) can be found at ftp://dkuug.dk/JTC1/SC22/JSG/. Looks like anyone can join the mailing list, and anyone can read themail. ftp://dkuug.dk/JTC1/SC22/JSG/926 and up are the messages since Sun formally chickened out of submitting, and the reaction on the list is consistant: what the hell is Sun talking about? There's also general dismissal of Sun's assertions that Microsoft did any lobbying at all on this issue.

    You can also see the members of the list at ftp://dkuug.dk/JTC1/SC22/JSG/list.