Slashdot Mirror


Sun will Open Java's Source

bckrispi writes "An announcement from Sun spokesman Raghavan Srinivas indicates that, contrary to what we've heard in the past, Java will be Open-sourced. "We haven't worked out how to open-source Java, but at some point it will happen," Srinivas said."

146 of 584 comments (clear)

  1. Boon by TWooster · · Score: 4, Insightful

    This is an excellent boon for open source software. Even if we only get small portions of it, having open-source Java can only benefit the community.

    Thanks, Sun!

    1. Re:Boon by ajs318 · · Score: 5, Insightful
      Depends what licence they use.
      • If they use the "sharing is not theft" BSD licence, then someone conceivably could take Java, modify it just enough to make it incompatible with the old version, and release their modified version -- let's call it EvilJava because I can't think of anything better -- closed-source. By writing plenty of code that only runs on EvilJava, someone can effectively usurp control of the market -- this, presumably, is the "nightmare scenario" Sun is keenest to avoid.
      • If they use the "not sharing is theft" GPL, then nobody can release a closed-source modification. Somebody could conceivably write a "JavaTwoPlus" incompatible with plain old Java, but it would necessarily be GPL. We have to assume that GPL automatically means cross-platform, since there would be nothing to prevent Sun themselves from porting JavaTwoPlus to any other platform for which a version of GCC exists.
      • If they go for a Pine-like licence, then nobody will be allowed to release modified binaries to the general public -- whether EvilJava or JavaTwoPlus -- in such a way that they could be confused with the "official" Java. Anyone wishing to create an improved Java would be confined to releasing patches for the source. As wonderful as this looks in theory, it's a nightmare in practice because of the problems it creates for distributors. Some Linux distros already don't include Pine, precisely for fear of running afoul of its licencing terms {You typically have to modify any source package ever so slightly to get it to work with your own distribution; that's what the configure process is about. The actual Pine licence doesn't make it clear that such modification is permitted. Even if the University of Washington turns a blind eye to some distros putting out a patched pine, there is nothing to say that one day it won't start coming down hard on distributors}. Sun presumably wants Java to be distributed widely, so should word the licence very carefully if following this route -- there is a real risk of alienating distributors.
      The question boils one of balance between code integrity and the benefits of Open Source. BSD doesn't assure code integrity or cross-platform-ness. Pine-like assures integrity but impacts negatively on distributability. GPL blocks any outright threats to code integrity and cross-platform compatibility -- but potentially leaves Sun with hard work to do.

      All that being said, if Java has enough functionality already then nobody will really feel the need to add anything else -- which, of course, is where the greatest single threat to cross-platform-ness comes from. Those few who do have special requirements which can best be met through modifications, probably will not be releasing their modified Java versions into the mainstream.

      Sun has up to now played the role of a protective parent, shielding the child (Java) from the worst elements of the outside, adult world (closed-source vendors who would take a beautiful product and distort it for their own ends). But children do eventually grow up; and after a point, when they have learned the dangers of the world, it becomes wrong not to set them free into that very world -- for all its dangers, it is still a beautiful place. If Sun has done everything right -- or even done just enough right -- then there is nothing to fear when Java makes the transistion from tightly-reined, closed-source child to well-balanced, Open Source adult with an existence of its own that does not depend on Sun.
      --
      Je fume. Tu fumes. Nous fûmes!
  2. eh by Josh_Borke · · Score: 5, Interesting

    so, java and solaris will be open source, and hardware will be free. so basically we'll be paying for our work?

    1. Re:eh by newhoggy · · Score: 5, Informative

      ESR has something to say about free hardware.

  3. Benefits? by Anonymous Coward · · Score: 2, Interesting

    How will this benefit Java?

    1. Re:Benefits? by MrWim · · Score: 3, Interesting

      Bug fixing, performance enhancements, porting to more platforms, inclusion in free software only (assuming thay release it under a free software liscence rather than just an open source one) distributions [read: debian] to name just a few of the advantages.

      Also, if it's free more people are likley to use it for developing free software

    2. Re:Benefits? by iamwill · · Score: 4, Insightful

      Not quite an accurate analogy... Java's a platform, so if they release the platform code, there's the potential that a grassroots inititive might cut the fat, and release Java Lite (Decaf). If not, just look for additional branches in the java hardware support tree. Linux is strong because it's fundamentally higher in the operating system food chain, running off a highly optimized kernel, on platform specific assemblers. Up until recently there haven't been many processors that have supported a native Java runtime, so everything's been run in a JVM. If anything, it's about performance and community involvement.

  4. In other news by pavon · · Score: 3, Funny

    Sun just announced that they have just created a new gaming division which is expected to release it's first title "Duke Nukem Forever" in the near future. The title will run exclusively on Unix systems including Solaris, and the Java Desktop, but may later be ported to other operating systems when the source as well as all artwork is released to the public domain. When asked how Sun can possibly give away every product they own and still make money, Scott McNeily made vague indications of revenue possibilies from their recently patented method of solidifing plazma in deep subterranean lairs.

    1. Re:In other news by Anonymous Coward · · Score: 5, Insightful

      Very Funny!

      People often don't realize how expensive/lucrative Enterprise Support is compared to the cost of H/W and S/w. Companies charge as much as 29-35% of the product cost as support per year and support is never discounted. i.e companies give away s/w and h/w worth a million and charge say 290k per year in support.

      Support/services is often the number 1 consideration in purchasing.

      So, I would not be surprised if sun's net revnues do not decrese after they opensource all of their s/w, including OS.

      Besides, why does Sun want to fix a bug for which there is no revenue tied? Sun might rather fix an obscure bug from a paid customer than fix the most popular bug. By opensourcing Java/ or OS, they will be opening a new maintenance channel for their platform while still making the same service revenues.

      In our company, Sun support team is respected and our IS claims it is worth all the cost.

    2. Re:In other news by carambola5 · · Score: 4, Funny
      When asked how Sun can possibly give away every product they own and still make money, Scott McNeily

      replied: "Simple... Volume."
      --
      IWARS.
      People, in general, disappoint me. Politicians even more so.
  5. Not much of an announcement by G27+Radio · · Score: 2, Insightful

    "We haven't worked out how to open-source Java, but at some point it will happen," Srinivas said."

    When I heard this earlier today I thought the same thing, this is a non-announcement.

    1. Re:Not much of an announcement by lucaschan.com · · Score: 2, Interesting

      When I heard this earlier today I thought the same thing, this is a non-announcement.

      It may be a non-announcement. But it's certainly more promising than what they've stated in the past.

    2. Re:Not much of an announcement by k4_pacific · · Score: 5, Insightful

      It doesn't sound that challenging. Slap a CPL on it and dump it on SourceForge. I think they are trying to figure out a way to make it Open Source, yet still retain control over it and derive revenue from it. Sooner or later, they are going to realise that they only have three choices, none of which are very good (for Sun):

      1. Java is not open-sourced and falls out of use like most closed standards eventually do.

      2. Java is released as open-source and they lose control of it.

      3. Java is released under a pussyfoot-shared-source-with-lots-of-restrictions- but-we'll-call-it-open-source license which alienates the OSS crowd and causes open rebellion. Same outcome as #1, only quicker.

      Overall, it doesn't look like Sun can win with this.

      --
      Unknown host pong.
    3. Re:Not much of an announcement by shaitand · · Score: 4, Insightful

      I disagree, there really is no value in sun controlling java itself.

      Sun own's the java brandname and wants to exploit that, that is there asset. If you want proof, look at the sun java desktop which has not the slightest thing to do with java.

      If turned over to the open source crowd java will be powerful and popular in no time. That means the word java will be used all the time, making sun's brand more powerful.

    4. Re:Not much of an announcement by Snoopy77 · · Score: 5, Insightful

      It seems from analyzing sourceforge that Java seems to be doing quite all right within the OSS community just as they are. Coming a clear third behind C++ and C is not bad in terms of language use.

      There is enough OSS built around Java to keep it alive in the OSS community and popularity as a whole is right across the board.

      They do have real concerns about losing control. Usually, without too much hassle, Java can live up to its write once, (test and then) run everywhere. Will this be so if there are forked projects?

      It would be great to get the OSS community in on improving Java but I can see why Sun want to remain in control.

      --
      "She's a West Texas girl, just like me" - G.W Bush Iraqis
    5. Re:Not much of an announcement by peawee03 · · Score: 2, Interesting
      They do have real concerns about losing control. Usually, without too much hassle, Java can live up to its write once, (test and then) run everywhere. Will this be so if there are forked projects?
      Hasn't Sun made Java an open standard, as in you can run a Java app on any VM that lives up to the standard? Thus, you can implement the standard however the devil you please.

      Please correct me if I'm just talking from the ass.
      --
      I wish I could write clever and witty sigs.
    6. Re:Not much of an announcement by bwy · · Score: 4, Insightful

      Good points.

      I wonder, with something as big as the whole Java world is right now, if you're not right.

      Take an OS, for example. Look at the difference between OS X and Linux. Linux is going in every which direction but has more potential than just about anything on the planet.

      Apple, however, took Free BSD and put a super nice wrapper on it. They've got managers who keep developers focused and executive officers who keep managers focused. Often, the open source community has a very narrow and selfish view when it comes to certain things. Like, why make software easy to install, like OS X? No need- any Linux user (present or future) is smart enough to compile his own software, resolve dependencies, etc.

      A person has to ask- could the OSS community ever have produced a gem like OS X? Could it have produced Java? OSS has the skillset, some of the sharpest folks on the planet. But who is keeping them coordinated? Who is the CEO with a single, cohesive vision?

      Don't get me wrong on OSS here. It has produced cool, big things like the Linux Kernel, Gnome, KDE, XFree86, etc., etc. All wonderful pieces of a puzzle that just doesn't seem to fit together quite as well as they need to when it comes to building a complete OS platform.

    7. Re:Not much of an announcement by Mag7 · · Score: 3, Insightful

      1. Java is not open-sourced and falls out of use like most closed standards eventually do.

      Wha..? Java is not a closed standard. See the Java Community Process. Sun's implementation is closed. I disagree that "most" closed standards fall out of use. Many survive.

      2. Java is released as open-source and they lose control of it.

      Well, the Linux kernal is open-source and yet Linus maintains quite a lot of control over it. No doubt Sun's people would still have a lot of control because they're the most familiar with it, and it is/was their baby. This happens with a lot of open source projects.

      3. Java is released under a pussyfoot-shared-source-with-lots-of-restrictions- but-we'll-call-it-open-source license which alienates the OSS crowd and causes open rebellion. Same outcome as #1, only quicker.

      Unfortunately I think that we'll see something like this. Rebellion? Well, no, people are using it now under its closed paradigm. Many people will use it regardless of its closed or openess (or varying levels in between).

    8. Re:Not much of an announcement by HiThere · · Score: 2, Insightful

      That's happening anyway.

      If I may:
      gcj, kaffee, jikes, etc. (I don't remember all the one's that I encountered.) Notice, though, that c, c++, Fortran, python, and Ruby (among others) haven't forked. At most there are dialects with extensions to the core language, or differing libraries. Well, unless you consider Objective C to be an incompatible fork rather than a separate language.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    9. Re:Not much of an announcement by Snoopy77 · · Score: 4, Insightful

      But as I understand it I can compile my java code under gcj, kaffee, jikes, javac and it will work. But what if someone, let's say Microsoft, comes along and uses their monopoly within let's say the OS market to push their own version of the java language and call it ... um ... J++. So people are out the writing J++ compaitable programs that won't run on anything but Windows. But they think they are writing in java cause it looks just the same.

      This is not what Sun wants.

      --
      "She's a West Texas girl, just like me" - G.W Bush Iraqis
    10. Re:Not much of an announcement by dbarclay10 · · Score: 3, Insightful
      Often, the open source community has a very narrow and selfish view when it comes to certain things. Like, why make software easy to install, like OS X? No need- any Linux user (present or future) is smart enough to compile his own software, resolve dependencies, etc.

      1996 called. They wanted to know why you're compiling from scratch as opposed to using a distribution and its package manager. (*cough* Debian, Red Hat, SuSE, Mandrake, Connectiva, Slackware, hell even Gentoo *cough*)

      --

      Barclay family motto:
      Aut agere aut mori.
      (Either action or death.)
    11. Re:Not much of an announcement by FooBarWidget · · Score: 4, Interesting

      "Often, the open source community has a very narrow and selfish view when it comes to certain things. Like, why make software easy to install, like OS X? No need- any Linux user (present or future) is smart enough to compile his own software, resolve dependencies, etc."

      Sigh... don't give me stupid stereotypes like that. I've been working for more than 2 years on the autopackage project, which is exactly trying to make Linux software installation easier. I've put many man hours into the project and you come up with a dumb stereotype!? I'm very insulted! I'm sure all the people who put a lot of efford into GNOME and KDE would feel the same way too.

      I swear, if Linux ever fails on the desktop, it'll be because people like you keep insulting developers with dumb stereotypes.

      "A person has to ask- could the OSS community ever have produced a gem like OS X? Could it have produced Java? OSS has the skillset, some of the sharpest folks on the planet."

      Yeah. How about Mono? Everybody who has tried .NET is bragging about how great it is. How about GCJ? It can produce native executables from Java source code. Perl and Python are also very nice and powerful languages.

      "But who is keeping them coordinated? Who is the CEO with a single, cohesive vision?"

      How about the project maintainer? The BSDs has a clear visiion of what it's supposed to be. Inkscape's maintainer has a clear vision of the future. There are good and bad maintainers, but there are also good and bad CEOs. Don't act like corporate control is some kind of bliss.

    12. Re:Not much of an announcement by TheRaven64 · · Score: 2, Interesting
      Apple, however, took Free BSD and put a super nice wrapper on it.

      No, Apple took OpenStep (or maybe OPENSTEP, I can never remember which capitalisation was the standard and which the OS) which was already a very nice 4.3BSD/Mach 3.0 derived OS with a consistent UI. They then replaced some of the 4.3BSD parts with FreeBSD 4.x (pre 10.3) and FreeBSD 5.x (post-10.3), updated the UI to look more shiny and added a MacOS compatibility layer. Going from BSD to OS X was something that took 20 years of continuous development from NeXT and Apple, not something that happened overnight.

      Don't get me wrong on OSS here. It has produced cool, big things like the Linux Kernel, Gnome, KDE, XFree86, etc., etc. All wonderful pieces of a puzzle that just doesn't seem to fit together quite as well as they need to when it comes to building a complete OS platform.

      Try running GNUStep and WindowMaker on X11 on *BSD. You get something a lot like OpenStep 4.2, with a few of the OS X improvements added. It's not OS X, but it's a very nice workstation environment and close to source compatible with OS X (you can compile GNUStep apps on OS X. The other way around works if the code is pure POSIX/Cocoa and doesn't use any of the newest features of Cocoa).

      --
      I am TheRaven on Soylent News
    13. Re:Not much of an announcement by bwy · · Score: 2, Interesting

      1996 called. They wanted to know why you're compiling from scratch as opposed to using a distribution and its package manager. (*cough* Debian, Red Hat, SuSE, Mandrake, Connectiva, Slackware, hell even Gentoo *cough*)

      Works okay until you find some app that isn't quite mainstream and still needs to be compiled. Even the smallest, oldest Win32 or Mac shareware app installs easily. Also, installing software on Linux doesn't seem to normally offer to put things in the Gnome or KDE menus, create desktop aliases, run at startup, etc.

    14. Re:Not much of an announcement by bwy · · Score: 2, Informative

      I swear, if Linux ever fails on the desktop, it'll be because people like you keep insulting developers with dumb stereotypes.

      No, it will fail because for years people have struggled with software installations, OS configurations, hardware configurations, etc. Yeah, wonderful that I have a choice of Gnome or KDE. You know what would be more swell? If I plug in a new monitor, and my X Server won't start, and I DIDN'T have to ssh into the box and manually hack the XFree86 config file before the box will boot at 5 again.

      Try explaining this type of thing to Joe User when he buys a new monitor at CompUSA and brings it home. I've been a software developer for many years and I've found the best thing that has benefited my career has been to drop the arrogance I had the first few years and start listening to the users, however "dumb" they might seem at first. After all, they're the ones using the stuff, and without them we just have a lot of OSS technology that is only useful to the development community. Oh, and users are only "dumb" at using PCs. Chances are they're using their PCs do do other types of work that you and I wouldn't have a clue about.

    15. Re:Not much of an announcement by FooBarWidget · · Score: 2, Insightful

      Uhuh, and flaming developers with dumb stereotypes and discouraging them to continue to develop will do the end users any good?

      I have nothing against making it easy for end users. In fact, that's exactly what I'm developing: easy solutions for end users. But insults and stereotypes from people like you is EXACTLY what I hate so much!

    16. Re:Not much of an announcement by bwy · · Score: 2

      PS: Since when is X unable to autoconfigure a monitor? I've never had this problem.. I conclude that you're trolling.

      Wish I were. RedHat 9- was running a 17" CRT, changed to an LCD, X wouldn't start. Had to ssh in and manually change the refresh settings and restart the box.

      I think, the typical Linux hacker is so used to doing all these types of things that they don't realize that an ordinary user would even have issues.

      I really think the downfall is the fact that people won't accept responsibility for an app or an OS not succeeding. It is always someone else's fault that Linux isn't used on desktops all over. It is Microsoft, it is the government, it is the evil PC manufacturers, or the evil peripheral manufacturers who don't supply drivers.

      Yet people are willing to pay for expensive hardware and a $120 a year for a new OS when it is Mac OS X, a UNIX-derived OS. Why? If you don't know the answer, then Linux is sure to remain on servers in data centers for the rest of eternity.

  6. opening questions by rd4tech · · Score: 3, Insightful

    The Java community is split over whether open-sourcing Java is beneficial.
    I will probably be marked troll on this one, but I have to ask:
    How in the world can you be split over something like that?
    I mean, people will basiclly poke at the code and report you bugs.
    Other developers will request tons of features that they will point how easy are to be done.
    Everyone will be happy.
    It's not as if they are charging people for using the pure java language right now.

    However, others, including Sun, believe the main hurdle and concern is the future of the Java brand and compatibility.
    So, they are planning to be constantly changing the language then? What are they smoking?

    We haven't worked out how to open-source Java -- but at some point it will happen," Srinivas said. However, he noted "it might be today, tomorrow or two years down the road".
    Well, you start with a 19$ .com name, 200+$ /month for the hosting plan, and about scores of thousands $ for a 2 pages legal agreement. It shouldn't be that hard....

    1. Re:opening questions by Anonymous Coward · · Score: 4, Insightful

      So, they are planning to be constantly changing the language then? What are they smoking?
      I think they're worried about someone forking it. What they ought to do is release the Java code under the GPL but not give up their trademark on the Java name. That way, forked versions can't call themselves Java unless they meet Sun's existing compatibility criteria.

    2. Re:opening questions by Chester+K · · Score: 3, Insightful

      How in the world can you be split over something like that?

      The fear of a fork is what keeps the community split. A truly open source Java would have no restrictions against someone taking Java and extending it in a way that's incompatible with existing Java (remember when Microsoft tried to do that?). It would completely undermine the idea of Java as a stable universally-compatible platform to build on.

      --

      NO CARRIER
    3. Re:opening questions by Tarantolato · · Score: 2, Informative

      The fear of a fork is what keeps the community split.

      Sun has this spooky, almost pathological, fear of forking. I guess you can attribute it to fallout from the proprietary Unix wars of the 80s and 90s. Thing is, those were a direct consequence of proprietary licensing. Everyone took the "historical Unix" code, put it in their own systems, and then chugged along incompatibly, with the new code hidden. The difference with GPL'd code is that if you use it, you have to publish it. So your rivals can copy or emulate incompatible features easily.

      GPL projects can fork, but the forks can dovetail back into one another. Proprietary projects that fork stay forked.

    4. Re:opening questions by FooBarWidget · · Score: 2, Insightful

      That argument is not very god.
      1. The most important question: WHY would anyone fork it? Where are the 'hundreds of forks' of Perl and Python?
      2. And just who the hell will actually use an incompatible, impopular Java fork, that isn't even legally allowed to be called "Java"?
      3. How's forking Java and making it incompatible any different from creating your own language with incompatible but similar Java-like syntax? (other than that under the hood it's based on Sun Java, but nobody cares about that)

  7. This is news? by Tesser · · Score: 5, Insightful

    Not to be a cynic, but "at some point" they will "somehow" figure out how to open source Java?

    And at some point I'll somehow figure out how to make a million dollars while sitting at home playing my Playstation, too.

    I fail to see how this qualifies as news.

    1. Re:This is news? by bruthasj · · Score: 2, Informative

      Because Sun is a fairly large company with a fairly widely used product and they're actually *considering* the possibility of open-sourcing that product, whereas before everyone thought it was some lone ranger rant by ESR. Besides, Sun is the only entity on the planet with the rights to make this decision.

      On the other hand, no one knows who you are, no one cares if you make money, everyone has a playstation, and most people know how to play it.

      Does that help put things in perspective?

    2. Re:This is news? by SenseiLeNoir · · Score: 2, Insightful

      Not quite.. Although both C# and Java "compile" to an intermediate code, whcih is interpreted (C# uses ICL, Java uses Java Bytecode), both Java and C# have something called Just In Time (JIT) Compilers.

      JIT's compile the bytecode into native code on loading of the classes. althoguh thsi could create a small dely on loading the classes, once loaded performance is often very good. I have created some processing software on Java, which i foudn performs almost as well as equivelent C code. In fact i foudn that if we were to code in C++ with all the "safeguards" in managed languages such as C# and Java, performance of Java is sometimes actually better than C++.

      A JIT is provided with JRE, however, the JIT can be replaced (on Windows it is a DLL, and the Java Control applet allows you to switch between different JITs, which may perform better in different cases)

      Finally there was a product called TowerJ, which takes Java source or Bytecode, and compiles it into a native executable, and althoguh the final product will definately NOT be write once run everywhere, previous tests shows it stonking all over most JREs and even giving C++ a massive run for the money..

      --
      Have a nice day!
  8. Bah! Tell me when it actually happens! by mrchaotica · · Score: 5, Insightful
    "We haven't worked out how to open-source Java -- but at some point it will happen," Srinivas said. However, he noted "it might be today, tomorrow or two years down the road".
    This is useless. Considering how often Sun changes its mind, there's no reason to believe anything they say. It'll only be newsworthy when Sun actually does it!
    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    1. Re:Bah! Tell me when it actually happens! by Bricklets · · Score: 4, Interesting

      This is useless. Considering how often Sun changes its mind, there's no reason to believe anything they say. It'll only be newsworthy when Sun actually does it!

      Considering just a month/few months ago Sun was saying no to open sourcing Java, this IS news. It represents a public shift in their coporate strategy. Call it what you will, this is newsworthy.

      --
      Little Bricklets
    2. Re:Bah! Tell me when it actually happens! by HiThere · · Score: 2, Insightful

      But they shift their strategy every week! Anyone who takes this seriously needs to look at Sun's history.

      When they release it, then perhaps the license will cause it to be news, or one sort or another. I.e., it won't necessarily be positive news. Remember, this is the company that came out with the SCCCL license.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    3. Re:Bah! Tell me when it actually happens! by Bull999999 · · Score: 2, Interesting

      Not to mention their stance on Linux. I'm still not sure if they are for or against it, although I personally think that Sun's anti-Linux.

      --
      1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
    4. Re:Bah! Tell me when it actually happens! by killmenow · · Score: 2, Insightful
      Okay, I'm coming to this late, I know. But, you said:
      It represents a public shift in their coporate strategy.
      I concur. However, the strategy is not (imho) what it seems. The noticeable shift in Sun strategy ever since the Microsoft $2,000,000,000 cash explosion (i.e., settlement) has been to do everything possible to cast a shadow on Linux competitors...Red Hat in particular.

      Now we have two recent announcements of open sourcing Sun's MAJOR software products with a vague "someday" air to them, which *reeks* in that way only a "oh, why use that product when we've got a better version that will be out really soon now" statement can. This is combined with recurring public statements by Schwartz attempting to introduce new memes into the I.T. sector ("open standards vs. open source") that (whaddayaknow!) serve to disparage the GPL, those who use it (Linux), and Red Hat *specifically*.

      Yes, it's a public shift in their corporate strategy all right. The enemy of my enemy is my friend. Microsoft and Sun have a common enemy that they both know will be the end of Microsoft's dominance and could quite possibly be the end of Sun, period, if they don't work in conjunction to slow it down.

      So, indeed, we agree also that this is newsworthy. If I'm not mistaken, we believe it is newsworthy for different reasons. You believe they mean what they say. I don't. I will believe it when I see it.
  9. faces of a coin by Anonymous Coward · · Score: 3, Insightful
    the optimist in me says "alright, about time." the pessimist in me says, "wait until it happens before rejoicing."

    I really hope they do open source java. it would let OSS improve the VM. it would make it evolve faster and allow more people to improve it.

  10. ANSI/ISO by NitsujTPU · · Score: 3, Insightful

    Java is nice and all, but I still prefer that my programming languages be managed by a standards organization.

    1. Re:ANSI/ISO by warkda+rrior · · Score: 4, Funny

      On the other hand, I prefer that my programming languages be managed by a garbage collector.

      --
      You need to install an RTFM interface.
    2. Re:ANSI/ISO by heathm · · Score: 5, Insightful

      Java is managed by a standards organization. It's call the Java Community Process. Any individual can join for free and contribute to the Java standards. Companies can join for a reasonable cost. Everything that goes into Java is standardized by the JCP and every JCP standard is freely implementable.

      Explain to me why we need ANSI or ISO?

      A colleague of mine insists that .NET is better because it's an ECMA standard. He's too dense to understand that not all of .NET is part of the ECMA standard and it's not truly an open standard because although I can freely implement what the ECMA standard says, I can't do jack crap to change what's in the ECMA standard. The standard is controlled wholly by Microsoft.

      Explain to me how this is better than the JCP?

      The JCP is already slow enough. The last thing Java needs is some bloated organization like ANSI or ISO to get involved.

  11. Not sure how? by leprasmurf · · Score: 2, Insightful
    I don't understand what trouble they are having with opening the source. Isn't as easy as publishing the source code?

    I guess I can understand the fear of losing the "write once, run anywhere" mentality, but if that's one of the main attractions to the language doesn't it stand to reason that people won't really veer to far off?

    --
    "And The Geek Shall Inherit The Earth" --Jeff Darlington
  12. Wow, this is huge news! by autopr0n · · Score: 2, Interesting

    Let me be the first to say: I hope to god Eric Raymond doesn't try to take credit for this. For those of you who don't know, ESR wrote an open letter asking for sun to Open-Source java. He wasn't the first, by a long shot. And IBM also asked for the same thing. Given ESR's tendency to take credit for just about everything though, I'm sure he'll claim that this was his doing...

    That said, I hope java doesn't end up fragmented. One of the really nice things about java is that despite a few problems, it's very portable. I've never personally had a problem moving my code from one machine to another. I hope we don't end up with lots of different "distributions" of java. While Linus has managed to keep the Linux kernel mostly whole, That has a lot to do with his political skills. Lots of OSS projects end up fragmented.

    I also hope this isn't an instance of sun trying to save some of their technology from being destroyed as their ship goes down. Sun has been struggling, and I hope they pull through and continue with their leadership in the development of java.

    --
    autopr0n is like, down and stuff.
    1. Re:Wow, this is huge news! by mrfibbi · · Score: 5, Insightful

      I think that people who worry themselves over the ominous and supposedly inevitable "fragmentation" really need to take a second look at things.

      1-There are numerous examples of open source programming languages that have remained centralized and unfragmented, like Perl and Python.

      2-Because java depends on a uniform standard and VM, any attempts to split off or fork the source tree will die miserably due to a lack of compatibility with the massive pool of existing code and classes.

      3-In fact, there is actually LESS chance of fragmentation when Java lies in the hands of the public, first because it means that no one will start up a competing "openjava", a venture that would almost certainly lead to incompatibilities, and second because, as the example of the death of xfree86 shows, too much central and absolute control over software by a small group will inevitably anger developers and users alike, leading them to search for an alternative.

      Honestly, this is slashdot. You people should have more faith in OSS.

    2. Re:Wow, this is huge news! by dmaxwell · · Score: 2, Interesting

      I'm treating this "announcement" strictly as a hypothetical musing. I truly don't know what to make of Sun's motives or intentions. You have to remember these are the people who would have you know that Linux is a good desktop but a lousy server. Sun can say and do so many contridictory things in the course of one day that I think Scott McNealy should tie it all up with dinner at Milliways.

      Assuming this is for real, Java needn't become fragmented at all. For one thing, Sun could choose one of the source under glass licenses and call it Open Source. That situation wouldn't be much different than what we have now save the PR bonus/controversy for Sun. It's a pity OSS didn't get their trademark; it would have cut down on that sort of thing.

      On the other hand, they could pick the LGPL or even the pure GPL and enforce the Java trademark ruthlessly. No one is going to bundle Joe-Bob's Virtual Machine. Besides, there is a vast body of code that any would be machine has to run. It takes extremely obnoxious behaivor on the part of the maintainers for such forks to even get started. Oh well, the possibility is interesting but doesn't really excite me.

      One thing they could do right now is fix their retarded redistribution terms. They need all the mindshare they can get. It is a PITA to have to install Java as a third-party addon in a Linux distro. They just need to fix whatever it is that stops Suse and Redhat from bundling with it their distros. It wouldn't even hurt much if it had to live on some sort of contrib CD.

    3. Re:Wow, this is huge news! by RAMMS+EIN · · Score: 5, Insightful

      ``That said, I hope java doesn't end up fragmented.''

      You mean, more fragmented than it already is with Sun, Microsoft, Apple, Kaffe, gcj, Latte, Jikes, and so on and so forth all providing their own implementations?

      ``One of the really nice things about java is that despite a few problems, it's very portable.''

      Oh yes. About as portable as C, Python, Fortran, ADA, Pascal, Common LISP, Scheme, PHP, Ocaml and a plethora of other languages.

      ``I've never personally had a problem moving my code from one machine to another.''

      You lucky bastard. You must never have moved your code developed with a modern Sun JDK to a machine using Microsoft's VM. Or an old (1.0.x or 1.1.x) Sun JVM, for that matter. Or tried running AWT code on pretty much any of the open source JVMs, which are kind of your only choice if your machine is not x86, PowerPC or SPARC, or the operating system is anyting besides GNU/Linux, Solaris, Mac OS, OS X, or Windows.

      Java is a dream that never came true:

      1. Write once, run everywhere is a myth, because you need a good VM and class libraries, which are only available for a few platforms.

      2. The official distribution is bloated to the top and runs slow even with JIT compilation. Java programs use lots of memory. This makes Java unnatractive even if you can guaratee it will work on your target system.

      3. GUIs in Java are a nightmare. AWT can be a bitch to code for, lacking many useful components. Swing uses "pure Java" widgets, which are slow and don't fit well with the native widgets on your system. SWT ought to be better, but is not included in the distribution, so if you want it, you need more bloat.

      4. High performance apps are out. GUI apps are a nightmare. What's left? Simple command line utilities? Nah, much better written in a different language. Whomever heard of multi-second startup time for hello world, and BufferedReader in = new BufferedReader(new InputStreamReader(System.in)); before you can do something useful with standard input?

      Oh yeah, it runs on cellphones. At least, the very much scaled down J2ME does. But don't expect good performance, and don't expect software written for some cellphone to run on yours. It's the same story again.

      Java has failed.

      --
      Please correct me if I got my facts wrong.
    4. Re:Wow, this is huge news! by dekeji · · Score: 2, Interesting

      first because it means that no one will start up a competing "openjava", a venture that would almost certainly lead to incompatibilities,

      Even though there are attempts at doing that, Sun's licenses prohibit it. If you have looked at Sun's source code or their Java specifications, any work you do on an "OpenJava" is a derivative work. So, the status quo is quite cozy for Sun: they really do not have to worry seriously about open competition because Sun has the legal means to squash such competition should it become a serious competitor.

      second because, as the example of the death of xfree86 shows, too much central and absolute control over software by a small group will inevitably anger developers and users alike, leading them to search for an alternative.

      You mean like the control Sun is exercising over Java? You see, that's what Sun really is afraid of when they talk about "forking": they are afraid that the developers and users they angered will pick another entity to take control of Java. You wouldn't end up with two incompatible versions of Java, you'd end up with only one, the one that doesn't come from Sun anymore.

    5. Re:Wow, this is huge news! by pjt33 · · Score: 4, Insightful
      You mean, more fragmented than it already is with Sun, Microsoft, Apple, Kaffe, gcj, Latte, Jikes, and so on and so forth all providing their own implementations?
      I thought Microsoft had been forced to stop fragmenting it by the U.S. courts. I know that Apple work with Sun, and the only real difference is that Apple write the native code.
      Oh yes. About as portable as C, Python, Fortran, ADA, Pascal, Common LISP, Scheme, PHP, Ocaml and a plethora of other languages.
      It's hardly a great insight that interpreted languages can be ported by porting the interpreter. It's possible to write portable code in the compiled languages you mention, provided you're careful and you provide copies of libraries for things like UIs, but you have the choice between compiling yourself on every target platform and distributing umpteen binaries, or distributing source and requiring the end-user to compile it. Doable, but it requires either superior end-users, or giving them a tool like Fink to handle everything for them, at which point you're back to doing the configuration yourself. With Java, you can distribute a jar and anyone with a VM can run it.
      You lucky bastard. You must never have moved your code developed with a modern Sun JDK to a machine using Microsoft's VM. Or an old (1.0.x or 1.1.x) Sun JVM, for that matter.
      Again, it's hardly a great insight that you need up-to-date libraries to run a program that uses libraries. The same applies to any language.
      2. The official distribution is bloated to the top and runs slow even with JIT compilation
      Define slow. 10% slower than optimised C isn't really slow.
      3. GUIs in Java are a nightmare. AWT can be a bitch to code for, lacking many useful components. Swing uses "pure Java" widgets, which are slow and don't fit well with the native widgets on your system.
      If Swing doesn't fit with the native widgets on your system, all you have to do is write a PLAF. I mainly use OS X, and Apple's libraries include a native-looking PLAF.
    6. Re:Wow, this is huge news! by autopr0n · · Score: 2, Informative

      You lucky bastard. You must never have moved your code developed with a modern Sun JDK to a machine using Microsoft's VM.

      Now why the hell would I want to do that!? Complaning about MS's "So non-standard we got sued over it" VM not being compatable isn't much of an argument. And you're right. I have mostly only moved code between JVMs that were modern for their time. But most of the machines I've ever had to deal with had 'em, so I don't see that as a very big deal.

      The beauty of java is that I can take compiled binaries (which I may or may not have the source too) and run 'em on 99% of the machines out there (any windows, apple, or Linux box basicaly)

      --
      autopr0n is like, down and stuff.
    7. Re:Wow, this is huge news! by six11 · · Score: 2

      I code Java for a living and couldn't agree more. I've only been doing software development for about eight years now, and I'm really beginning to feel that I made a mistake by concentrating too much on Java, for exactly the reasons this guy lists.

      A couple of other comments to the parent post were in the vein of "D00d, U need to stop yer bitching and look at the good things about Java". No offense to those posters, but I think they don't have to use Java in the less-than-good places for a living. Sure, Java on the server is great. It's in a position that you can control, so you can (will be able to) take advantage of the goodness that is 1.5. However, Java on the client... well, there's a whole host of reasons why my company is going to be porting our client applications from Java to a cross-platform natively-compiling version.

      The problem with Java on the client is that you depend on the end-user to have things set up 'correctly' on their end. In our case, these are lawyers and accountants and other assorted people who could care less about computers. So if you discover that Java 1.3.1_06 and below has a fatal bug in the networking code, you have to write a workaround for that, since it is untenable to ask your customers to install a new JVM, and you also can't simply replace the buggy code. Our code is littered with places where we have to test things like "if the browser is Netscape 4.7, use this code, or if it's IE 5 use this code, but otherwise use this code, unless it's java 1.4.0 in which case it won't run at all due to bugs in the core java classes...". To me, this is a description of a language/runtime that has failed as a viable option for a client platform.

      At this point, somebody is thinking of posting as an AC something in the line of "D00d, U need to stop bitching and use SWT" or some drivel like that. Please don't post that, unless you can suggest something that won't force us to have to
      - write workarounds for the umpteen-hundred bugs related to browser X on platform Y using language version Z
      - force the user to download a 14 MB plugin
      - inflate our code from 400k to 3MB because of statically-linked VM bootstrap code
      - write code that depends on a platform that keeps changing

      That said, the parent post is right on the money, and I wish Sun would see that.

    8. Re:Wow, this is huge news! by Bob9113 · · Score: 2, Insightful

      I code Java for a living and couldn't agree more. I've only been doing software development for about eight years now, and I'm really beginning to feel that I made a mistake by concentrating too much on Java, for exactly the reasons this guy lists.

      While we're getting the credentials out of the way, I started coding in 1979. I've written commercial code in a lot of languages, from C to LISP to Python (just to name a few that cover a good chunk of the spectrum of language types).

      The problem with Java on the client is that you depend on the end-user to have things set up 'correctly' on their end. In our case, these are lawyers and accountants and other assorted people who could care less about computers. So if you discover that Java 1.3.1_06 and below has a fatal bug in the networking code, you have to write a workaround for that, since it is untenable to ask your customers to install a new JVM

      I'm presently employed on a cross-platform Java application. We have synchronized deployments to 3500 client machines that have to occur over a single weekend, and travel via our WAN to roughly 40 states plus Europe and Asia. The clients know not and care not how the application works. We ship a new JRE with roughly 20% of our deployments. Our application is currently deployed to Linux (client and server), Windows (client side only), and Solaris (server side only).

      How is this practical? Our application is over a million lines - the JRE isn't the largest part of the deployment. In enterprise deployments to a heterogenous environment, the key factor is not the size of the JRE, it is the things that really affect the bottom line - maintainability, platform neutrality, performance (yes, performance - Swing is within 10% of C when written properly), etc. I'm not saying Java is head and shoulders above all competitors in these areas, but it is certainly a decent match against the best of them. Every language has it's ideal areas - for my money (and having solved the problem with a number of technology sets), enterprise scale GUI client/server apps is one area where Java is well suited, as are some other languages.

      It's a toolkit. If you're having troubles with Java, try some other languages - you may find that others are more suited to your development style or your deployment environment. Java is not a bad language because the JRE is over 10 megs any more than an airplane is a bad form of transportation because it requires an airstrip. The right tool for the job is the key.

  13. Re:Yeah, by IBM. by 0racle · · Score: 5, Insightful

    I really can't see any good reason for Sun to open Java or Solaris. They won't accept patches unless the copyright is assigned to them, and Sun will have a license that wont allow code from GPL work to enter Solaris or Java and vice-versa. If they really did, I would take it as more of a "We Give-Up" move just before everything falls apart. I personally would hate to see Sun go.

    --
    "I use a Mac because I'm just better than you are."
  14. Do it where it counts! by newhoggy · · Score: 5, Insightful
    "We haven't worked out how to open-source Java -- but at some point it will happen," Srinivas said. However, he noted "it might be today, tomorrow or two years down the road"

    Instead of waiting two years, do it now when it counts most. If Sun feels some degree of uncertainty, then test the waters by open sourcing selective parts of the JDK - especially the parts of the Java libraries that are widely perceived to be neglected.

  15. Indonesia and the Pacific by Anonymous Coward · · Score: 5, Funny

    The true source of java has been known for many long years now: "The best Java coffee is grown on the far eastern end of the island on five estates established by the Dutch government." Evidence.

    warmest regards,
    Juan Valdez

  16. It's just another step towards obsolesence... by iamwill · · Score: 5, Funny

    You gotta admire the effort Sun is making to even maintain Java, anymore... Bless their hearts.

  17. Re:Yeah, by IBM. by SphericalCrusher · · Score: 2, Interesting

    Well, nonetheless, if Sun somehow dies, the world still has Solaris and Java at their fingertips. I can't believe they are actually going through with this. I thought that little Microsoft deal would have stopped it completely, but I guess Sun still has a few tricks of thier sleeves. w00t!

    --
    "Instant gratification takes too long." - Carrie Fisher
  18. Not really that big by leshert · · Score: 4, Insightful

    It's not nearly as big a deal as open-sourcing, say, Solaris, simply because it's not going to wreck a primary revenue stream for Java.

    I've wondered for a while where Sun makes money from Java, particularly enough to recoup what they spend on it. I can't imagine it affects sales of Solaris boxes that much.

    1. Re:Not really that big by molarmass192 · · Score: 2, Insightful

      The make some money on J2EE certification, mobile device runtimes, and licensing the Java trademark -but- the true value of Java to Sun is that it's the only thing that's keeping them relevant right now. Take Java out of the picture and Solaris would be on the brink of extinction like HP-UX and AIX. FWIW, I was a big supporter of Solaris up until the 2.4 Linux kernel made it's appearance.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
  19. Fork by Anonymous Coward · · Score: 2, Informative

    The problem with this is that it could cause people to make incompatible forks of Java. What I mean to say is that Microsoft could make a .Net version of Java that is not compatible with everything else.

    Not possible, you say. Who would use it.

    Well, whats the most vulnerable part of Java -- its the UI. Swing apps are pretty good already, but not quite comparible to a native app. Well, thats the first thing that will change. And people will like it because it feels like a native app.

    What for, you say. Just use SWT.

    Well maybe, but with .Net you get all the native widgets without a 3rd library in there. Plus, you can do something like System.Window.Form.Whatever. Shit I don't do .Net, you know what I'm talking about.

    1. Re:Fork by shaitand · · Score: 2, Informative

      Not if it's properly gpl'd, then Microsoft won't touch it with a 10ft pole. Some obscure unix tools for windows package is one thing, something like a jvm for .net is WAY too public to use under the gpl after their past statements.

      As for non-commercial forks... this will prevent them. Anyone can write a jvm NOW, there are already open source jvm's. Sun's isn't even the best jvm, but what sun has going for it is that it's the official jvm, that's true no matter what license it's under. If you want a jvm, it's sun you get it from.

  20. Is Microsoft Behind This? by javacowboy · · Score: 2, Insightful

    Call me paranoid or even a conspiracy theorist, but what if Microsofy is behind this? What if Microsoft, as part of their settlement with Sun, asked them to open-source Java so that they could embrace and extend it, and pollute it as they tried to before?

    How much do you want to bet that Java will be open sourced under a BSD-style license, and not the GPL.

    --
    This space left intentionally blank.
    1. Re:Is Microsoft Behind This? by Bricklets · · Score: 2, Funny

      Call me paranoid or even a conspiracy theorist

      Well, you said it first...

      --
      Little Bricklets
  21. Bad Move by atehrani · · Score: 2, Insightful

    I think Java is fine the way it is. Open Sourcing it will not bring any improvements and actually might hurt Java.

  22. Java for amiga anyone? by tcc · · Score: 3, Interesting

    Does that mean that finally, 10 years later, my amiga 1200 will finally have support for not only frames but java too? :)

    I remember the browsing frustrations I had in my last years on that platform, at one point we were in advance for just about everything possible, then lost to 3d gaming, then 16bits audio, then lost all the cool hacks like running a multi-line BBS routed through both telnet and dialup at the same time without even being a programmer, to being a slow about to die dog exept for playing speedball... Oh well.. better late than never I guess..

    --
    --- Metamoderating abusive downgraders since my 300th post.
  23. At some point! by ElDuderino44137 · · Score: 2, Interesting

    *Laugh*

    I'm sorry.

    I can't believe that an organization would put so much time, effort, and money into a product ... only to give it away to the open source community.

    Open source.

    Maybe when we all give up on Java and move to the CLR.

    Cheers,
    -- The Dude

  24. Compile once, run anywhere (even a fedora box) by j1m+5n0w · · Score: 4, Insightful
    How will this benefit Java?

    It will certainly increase its adoption, especially in the open source world, thus fulfilling its original purpose: write once, run anywhere.

    -jim

  25. Too little, too late. by digitaltraveller · · Score: 5, Interesting

    Let's assume this isn't horseshit fed to the masses to keep using Java technology.

    (eg. like dressing up in a Penguin suit while handing SCO a paper bag full of money under the table.)

    From a business point of view, what's the point?

    Mono is nearing release 1.0 and is a very attractive platform for developers. Releasing Java open source 3 years ago would have screwed Microsoft hard, but now I'm not so sure.

    I still think open sourcing is the best strategic move for Sun, but I think they have no clue on how to exploit it. They will probably do something silly like release it under the IBM CPL since that's what their competitors are doing.

    The best move for them is obviously to GPL it, and use a Trolltech style licensing model. GNU Classpath will naturally get in the way. (again, should have did it 3 years ago).

    However, the COO, Johnathan Schwartz recently teased in the media that they might release Looking Glass, Sun's new 3D desktop widget toolkit as open source. I've seen it, it looks great.

    If they GPL'd that as well, Sun might have a chance at getting a serious revenue stream happening.

    I doubt this will happen though. Sun will keep withering out of fear and inertia. It's the nature of the beast.

    1. Re:Too little, too late. by Jotham · · Score: 4, Insightful

      Mono beta 2 now includes a Java VM. "allows Java and .NET code to run side-by-side. It contains the latest release of IKVM.

      Sun's Java Class Libraries are very nice and full featured, if Java was open-sourced, I'd see Mono and Java merging together quite nicely. Write in whichever language is most comfortable, and call whichever API does the job the best.

      I see this as a good solution for Sun which is seeing developers leaving for .NET, turn to them and say, you can still use Java.

  26. Sun's Open Source Java mini-HOWTO by Alwin+Henseler · · Score: 2, Insightful
    In chronological order:
    • Determine conditions that Sun is sure of it finds acceptable right now for released files
    • Throw release files & those conditions on some big-iron ftp/http server under Sun's control
    • Make public announcement (& hopefully survive being /dotted ;o)
    • Inlude in conditions the option to submit patches to Sun
    • Include in conditions the option to publish patches to everyone else
    • Give selected regular patch-submitters limited write-access under strict additional conditions
    • Relax those conditions as time goes by, and you see the source base evolving nicely
    • Move source depository elsewhere, to make that big-iron ftp/http free for newer, more interesting projects
    Just my suggestion for how Sun could do it
  27. Why it might take some time... by stienman · · Score: 5, Insightful

    The reason they don't know how long it'll take is likely due to licensing agreements, patent royalties, and other little issues encumbering the code, on top of the normal burocracy.

    Inevitibly, in large organizations with large projects, some manager attempts to (and often succeeds in) shortcutting the development time by licensing or purchasing some outside code or technology. I would be surprised if Sun's implementation of Java was completely developed in house and/or completely owned without exception by Sun. They have to vet all the code and modules to be certian that they have the right to release Java. I doubt they'll release the unencumbered parts before it's all ready.

    Further, there are likely to be patent and legal encumberances to the code which may prevent immediate release. It could even be that people along the line have said, "I'll patent this technique later, for right now it's a trade secret." There may yet be code in there which they can capitalize off of by patenting, while allowing for usage within java without charge.

    And, of course, they have to make sure the company lawyers and accountants are satisfied with whatever terms they release it under. They may even wait until the SCO thing blows over if they really want to use the GPL (Unlikely).

    So don't hold your breath. The ideal outcome would make one able to compile it for platforms which it does not yet run on natively and stable.

    -Adam

  28. Re:Yeah, by IBM. by whereiswaldo · · Score: 3, Insightful

    I really can't see any good reason for Sun to open Java or Solaris.

    Me neither. Where the hell is the value in their company? Solaris doesn't have the greatest market share, and I see Java as their biggest strength. They want to give it away why? Don't they have a responsibility to the shareholders?

    People run all kinds of Microsoft-made technologies and don't gripe. What's with the shitstorm about Java not being open source?
    Who cares?

  29. It IS hard to open source java.... by bigman921 · · Score: 5, Informative

    Remember that java isn't just the jvm or the class library source. It also includes JSSE, java's encryption framework which probably can't be open sourced (comercial restrictions, export laws, legal liabilities of possible changes to shipped trusted certificates...). I am sure there are other pieces that are sensitive as well. You wouldn't be able to use SSL out of the box with a JRE that didn't have a JSSE implementation.

    --
    "So you call this your free contry, tell me why it costs so much to live?" - Three Doors Down
  30. Re:Yeah, by IBM. by Gerdts · · Score: 3, Insightful
    Absolutely right. That mechanism would never work.
    Before incorporating significant changes, make sure that the person who wrote the changes has signed copyright papers and that the Free Software Foundation has received and signed them. We may also need a disclaimer from the person's employer.
  31. Sun Benefits? by eeg3 · · Score: 3, Insightful

    Of course the opening of Java's source will be neat for "the community," but it doesn't seem like a very smart business move for Sun. There might be some temporary benefits in publicity, but no real benefits in the long run. Atleast if they keep it closed, they'll retain some control, and have the ability to possibly make money off of it.

    However, i'm sure they know this, and that's why it's not being released now, and it probably never will be, unless they somehow conjure up a way to release the source and retain complete control of it.

    ...Which seems impossible to me.

  32. jvm by sumdumass · · Score: 4, Insightful

    I would be happy if they just opensourced the virtual machine so distros can include it instead of me having to jump thru hoops getting it installed and working. Aslo this might allow different distro's to tweak the VM so it can run smoother and faster on thier version of linux while still supporting the develope once run anywere model. I'm not sure what else is in sun's java offering, I asume there would be an aplication server, a developers ide and maybe some other stuff.

    Sun is giving the VM away as it is, It would be nice to have it gpl compatable so it can be used right after an install.

  33. Re:Yeah, by IBM. by fmorgan · · Score: 2, Insightful

    Well, US-based organizations (from Sun to FSF) tend to be more "lawyer aware". But even Linux is moving into that direction now.

    This "They won't accept patches unless the copyright is assigned to them" is just the price of doing business in the US. Mostly to have copyrights clear and avoid SCO-like messes. Even if SCO claim is completely without merit (and that I believe so), you need to prove it.

    or, as someone said sometimes around 50 BCE said, "the wife of Julius Caesar doesn't only need to be honest" - don't remember the exact term - "she also needs to look like it".

    Suppose that someone has some java changes introduced and then, 1 year later, SCO claims it came from their code!!!!

  34. JMF Comes to Mind by ink · · Score: 3, Interesting

    Poor JMF; it's all but abandonded by Sun -- and the reference implementation pretty much only works on Windows for anything other than simple audio. IBM seems to be doing more development on JMF than Sun does anymore. The JMF forums are full of questions with very few answers. This would be an excellent library to open source.

    --
    The wheel is turning, but the hamster is dead.
  35. Open source, public source, or shared source? by Anonymous Coward · · Score: 3, Insightful

    It makes perfect sense if Sun is doing this for the same reason Apple open sources the internals of Mac OS X.

    Allowing their users access to the source to Solaris-- even if the license is "poisoned" to prevent it from being mixed with GPLed code-- would help Sun's users. They would be able to adapt the OS to strange fine-tuned uses and arcane hardware, or more easily debug kernel plugins. A shop that might otherwise have gone "well, we like solaris, but we don't want to be limited to sparc and x86, so we'll go with linux" might be dissuaded.

    Allowing their users access to the source to the JVM-- even under a GPL-incompatible license-- would do the same. It would allow Sun's users to port the JVM to those few platforms Sun doesn't support yet, or more easily debug JNI software.

    This is definitely a benefit for Sun's users. It makes both Java and Solaris more attractive. It makes a lot of sense.

    If they really did, I would take it as more of a "We Give-Up" move just before everything falls apart.

    Sun refuses to open source Java: Slashdotters interpret this as a sign they are dying.

    Sun agrees to open source Java: Slashdotters interpret this as a sign they are dying.

    Hmm.

  36. Re:Yeah, by IBM. by sumdumass · · Score: 5, Insightful

    Well, i'm not sure how sun is making a ton of money off of java now. They give the virtual machine as well as the web client away as it is. Maybe it is somethign to do with thier java desktop wich I asume won't be gpl'ed. Maybe if "opening the source" will get things runing faster and a little smoother There would be more of an market for thier desktop system.

    AS far as running microsoft and liking it? Thats because it is there. Most people won't even look under the hood and care, with java, people are going out ang getting it so they know what is there and more of the people using it are the ones that would bitch about microsoft. The difference is the amount visible to the public. Microsofts users would have more that didn't care where java users would have more that did care.

  37. actually, by jbellis · · Score: 4, Insightful

    When Jonathan Schwartz spoke at the Utah Java Users' Group he said Java drives a LOT of server sales for Sun. He specifically mentioned embedded java, e.g. in cell phones, as opening new revenue areas for servers. Java licening fees themselves are a drop in the bucket relatively.

    It will be interesting to see what kind of license Sun goes with given their oft-given fear of forking Java. Seems to me that something like the Qt license would be the way to go.

  38. Re:Yeah, by IBM. by gabebear · · Score: 4, Insightful
    The shitstorms are because Die-Hard Linux geeks/distros want to have everything on their computer/CDs under the GPL. If they don't put it out under a GPL compatable license then this exercise will be utterly pointless.

    IF they release it under the GPL, I see this making the open-source world a lot friendlier to Java. IF thy release it under a GPL licence, then KDE/GNOME will integrate java more closely(I.E. standardize).

    I think the smartest move would be for Sun to relase Java's source under the plain old GPL, but not let any implementation use the Java trademark unless it meets their criteria( so they can keep Java from fragmenting)

  39. What's the problem, exactly? by mi · · Score: 5, Informative
    FreeBSD ports of JDK 1.3 and 1.4 both build from source. Yes, you have to download the source manually from Sun, but it is available, and has been for years...

    Is it really that important to be able to distribute the built binaries for people? Without paying Sun for it, that is?

    --
    In Soviet Washington the swamp drains you.
    1. Re:What's the problem, exactly? by Anonymous Coward · · Score: 2, Insightful

      What's important is being free to actually *use* the source code. With Sun's current license, you can't do anything more than look at it. You can't use some of the code in some other project. You can't fix bugs or add optimizations and then distribute your version. With an open source version, Sun also wouldn't be able to change the conditions whenever they wanted to.

    2. Re:What's the problem, exactly? by samhalliday · · Score: 3, Informative
      further than all that... even the binary license is strict; if you distribute the SUN java in your OS distro... then you are not allowed to distribute ANY other replacement, i.e. gcj. thats pretty much why debian don't even have it in non-free and you have to add unofficial mirrors in your download lists

      "open sourcing" java doesn't really excite me too much... but, along the same lines as what you are saying, making it "free" (as in freedom) and GPL compatible would be a tremendous step, and i might actually start to learn some java! open sourcing somethign does not necessarily imply th freedoms that we are used to in the GNU and BSD worlds, despite all of those applications falling undert the open source umbrella (i consider open source tp be the supersets of all licenses which allow you to see the source code... but do not necessarily grant you the freedom to use it).

  40. encryption is compatible with open source by Great_Jehovah · · Score: 2, Informative

    The regulations clearly state that if you can point to the source you don't need permission from the government.

  41. Open Sourcing java is just more PR . by DRWHOISME · · Score: 2, Insightful

    Do any of you ever ask yourselves why now?

    Do you trust Sun ? They are excellent at manipulating the media.

    Sun is doing this for themselves so they can 'hype' more java news on all the internet news sources(zdnet,cnet,slash) and also pull more people into their language(prosyletize) so that they can cash in.

    Microsoft and Sun both proselytize.

  42. Re:Yeah, by IBM. by CallMeCal · · Score: 5, Interesting
    I'm no coder, but I believe that the GPL is the only thing that can save the (virtual) world. Saving the world, virtual or not, is bloody inconvenient.

    By a strange set of circumstances I found myself, a little over a year ago, sitting in a small room with RMS and a standard-issue complement of corporate Win32 support slaves. A FOSS missionary had brought us all together.

    I've been a GNU/Linux user since 1997. At home I am now exclusively a G/L user. Am gunning for that at work.

    Yet, when RMS told the gathered geeks and semi-interested bystanders (and I paraphrase) I think one should be willing to use inferior free software instead of superior closed software (/paraphrase) I thought Bull fucking shit.

    That was before SCO filed suit. That was before I paid enough attention to what's going down in the patent realm. That was before Redhat sold out freedom for whatever it is they think they're getting in exchange for freedom. (The money ain't worth it, guys. You know in your souls -- if you haven't sold them -- that it ain't.)

    I was running Redhat then. I'm running Debian now. It's inferior in many respects. It's maddening in many respects. It's free. I'm free.

    People who have more chops than I compile their own custom kernels and their own sets of GNU & other FOSS. That's not just freeom. That's power. That's one future that any user is free to choose.

    I'm so grateful to those who code in the name of freedom. I am writing this to you on a computer that's as free as I know how to make it, because of Richard Stallman, Linus Torvalds and thousands of like-minded coders.

    If, in order to stay free, I have to sign an effing affidavit every time I log on, I will do it.

    And I know the coders who believe in what they have taught me to believe in will take the time to certify their code. It's a *very* small price for freedom.

  43. You're not thinking. by SatanicPuppy · · Score: 4, Insightful

    If you develop in java, you don't have to pay sun any money. Sun uses what they call a "protected source" license, which basically says, "Anyone can use this, but only we can make changes, or release new distributions."

    Open sourcing java wouldn't really hurt them, and god knows java could use it.

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    1. Re:You're not thinking. by Anonymous Coward · · Score: 3, Funny

      and god knows java could use it

      Actually since god has never used a computer and wouldn't give a shit about Java, and since he's a figment of your imagination anyway, he actually doesn't know that Java could do with being open sourced. Hard to believe, I know. But that's the truth of it.

    2. Re:You're not thinking. by Decaff · · Score: 4, Insightful

      Open sourcing java wouldn't really hurt them, and god knows java could use it.

      Why?

      Is Java suffering at all due to lack of demand?
      No.

      Is the Java licencing restricting its implementation on different platforms?
      No.

      Is Java on Linux suffering as a result of this licencing?
      No - Linux is one of the main deployment platforms for Java.

      Is the demand for Java in the job market decreasing?
      No.

      I fully support open sourcing Java, but it does not take much understanding of the IT industry to realise that Java certainly doesn't need open sourcing - its phenomenally successful.

    3. Re:You're not thinking. by teromajusa · · Score: 2, Insightful

      It needs it because it needs to be more flexible to deal with the approaching threat of .NET. The IT world changes quickly. You have to adapt if you want to survive. Sun can try to do it on their own, or they can make it a community effort.

    4. Re:You're not thinking. by Decaff · · Score: 2, Insightful

      Yes - C# from Microsoft might pose a real threat to Java and make Sun redundant.

      Only if there is a full-featured .Net available on AIX, Solaris, IBM Linux, HP Linux, mainframe systems (still a multi-billion dollar market), Mobile phones, most PDAs, embedded systems etc.

      Until then, its a neat way to develop for Windows platforms, and to experiment with Mono on Linux.

    5. Re:You're not thinking. by Decaff · · Score: 2, Insightful

      If .Net is done right, and from the looks of it Microsoft has done it right, it will overwhelm Java for the simple reason that Microsoft has 95% of the desktop market.

      No. Its about 80-85%. Otherwise, figures for Linux installations and MacOS/X + Windows would add up to more than 100%

      Certainly future Microsoft OSes will run .Net out of the box. Actually .Net will probably run out-of-the-box on Linux AND Windows in the future, thanks to the work of what is now Novell. Java won't work out of the box except on a small handful of OSes (because the community rejects its license in favor of others.) If you can't see the demise of Java in the not-so-distant future, you must have your eyes shut.

      You are confusing desktops with the entire IT market. Java works NOW on almost every OS. If its not installed, its a single click to download and install from java.net. Major computer VARs like Dell are bundling Java with desktops. However, for general use, this is irrelevant. Most java apps are accessed by web pages, and most java apps are deployed on servers: Desktop software is irrelevant to the Java market.

      If you believe Java is in decline, you need to open your eyes and look at the real IT market, not the one you want to exist.

    6. Re:You're not thinking. by Decaff · · Score: 2, Interesting

      I think really that it is the frameworks that will keep Java alive.

      Good point, but there are several key features that will keep java not just alive but thriving.

      1. Absolutely key: Java is multi-platform. Even Microsoft now seems to be admitting that they will have to share the server market. Java runs on all servers - even Microsoft. Using toolkits like SWT, Java can have the same access to the Windows API as any other Windows app. As far as I can see, the only reason to use .Net is political, not technical: you want to ensure your apps run only on Microsoft platforms. Java does what .Net does, but does the same everywhere.

      2. Supported by lots of vendors. Even vendors who are in competition: Sun, IBM and HP, support Java and implement the standard.

  44. java or the JVM? by acomj · · Score: 4, Insightful

    I keep wondering if they mean the java class libraries or the Java virtual machine (which runs those java applications)?

    Opensourcing can only help java. It will definetly spread its adoption to be standard on many linuxes.

    1. Re:java or the JVM? by kiyut · · Score: 2, Interesting

      As the parent post said, the Java Term must be defined more clearly.

      Java Language: It is how you define the language itself eg: language syntax, primitive type, etc
      Java class library: It is the default library that come with the package eg: everything that start with java.* package
      Java VM: the runtime environment that execute the Java Class e: Sun Java VM, IBM Java VM, Kaffe, etc
      Other: not clearly defined & buzzword like Java Platform, EJB etc

      The Java Language itself is already Open in term of JCP, everyone can join and participate
      There are also many third party Java Library either OSS or Closed that complement the default Class Library like Apache Jakarta commons, various Java Widget.
      I think since Java 1.4 sun allows endorsed package/lib which mean third party library can replace the default lib ship with the Java VM

      Therefore, IMHO, the most needed OSS java is the Java VM. Because currently there are no Java VM implentation which is as complete as Sun Java VM. And Sun Java VM maybe the most featurefull but is it the fastest out there?
      By OSS Java VM it will allow:
      - freely distribution, eg many Linux vendor doesn't included Java VM in their community release
      - Improvement in Java VM performance, Java 1.5Beta is quite fast, but faster doesn't hurt anyone :)

      --
      Sketsa
      SVG Graphics Editor
      http://www.kiyut.com
  45. Re:Yeah, by IBM. by Bull999999 · · Score: 4, Interesting

    Apache isn't GPLed but that didn't stop most distros from making the Apache the standard web server for Linux.

    --
    1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
  46. Hell Yes! by twocents · · Score: 2, Interesting

    It's not so much about whether or not Java is Open Source. It's about the fact that when Java IS Open Source, then all of those other groups/companies/developers that make OSS products related to Java will push this technology even harder.

    It's already working. Come on, C# is borrowed from Java. If you have a hard-on about about M$, then just remember they took the idea and applied it to their own technology. The biggest computer software company in the world has already created products from Java.

    And don't forget, .NET only runs on Windows! Choice my ass, it only runs on Windows. If I repeat that again, am I a troll?

    Oops...my original point was that open sourced Java will help to push an industry into more development, very similar to the great amount of work that has come from working with Apache.

  47. Java's Second Comming? by MrRage · · Score: 2, Funny
    "We haven't worked out how to open-source Java -- but at some point it will happen," Srinivas said. However, he noted "it might be today, tomorrow or two years down the road".

    No one knows the day or the hour of the coming of source, not even the Sun...

  48. Don't fear the fork by ChiralSoftware · · Score: 4, Interesting
    Everyone is so afraid of forks. I think a fork would be great. How about KDE-Java, which is a Java distro for writing KDE apps? Why shouldn't I be able to write Qt apps in a safe, easy-to-use language like Java? Sure, it's a fork and that QtJava app won't work on any other Java, but that exists already. I'm told that a bunch of OSX apps are actually written in Java and the system has good support for that. What would be bad is tampering with the java.* packages, but there is no need to. Just make a Jaav distro with a trolltech.* tree built in and ship that with KDE... that would be great. Another option would be a Java fork that implements Swing using Qt for its rendering, instead of using X calls directly. That would also be a fork, because it would introduce a dependency on the Qt libraries into Java, but Java apps wouldn't change.

    These are just some examples of what Open Source Java could bring, and why forking is good.

    ----------
    Create a WAP server

    1. Re:Don't fear the fork by damiam · · Score: 5, Informative

      QT/KDE Java already exists.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:Don't fear the fork by SenseiLeNoir · · Score: 2, Insightful

      That option is not needed. Java is a PLATFORM INDEPENDANT language in which the core funtionality should NOT be tied to a particular platform.

      This is EXACTLY what MS did with Visual J++ and their own JRE. This is exactly what Sun fears about open sourcing Java.

      If you want a KDE specific version of JAVA, create the appropriate Plug-in/Replacement classes for the AWT/Swing. The current JAVA jre spec DOES indead allow that. Or if you are particularly brave, create new packages such as org.kde.*. The advantage of this approach is that it would run with ANY implementation of JAVA, not just the Sun, or Custom KDE JRE.

      A good example of this is WABA, a Java Like language/platform for Palm OS and Pocket PC. It uses its own set of packages (waba.*). However, the best part is, because its built on JAVA specifications, software can be developed and compiled on ANY JDK (I have tried Sun Forté, and Visual Café). This is just by adding the appropriate waba package for Java. This clearly demonstrates the pure power of Java.

      Although Open sourcing Java is good, I do understand their fears of forks. And it has happend befor e(MS VJ++)

      --
      Have a nice day!
  49. Re:Yeah, by IBM. by anshil · · Score: 3, Insightful

    I can see a good reason, having a real OpenSource license for java would give it a significant popularity and usage thrust. Something they could really use in the battle against .Net

    Java to be successful in the long term needs to be standarized and opened like C has been!

    --

    --
    Karma 50, and all I got was this lousy T-Shirt.
  50. It was bound to happen by Anonymous Coward · · Score: 2, Insightful

    Let's face it: It was bound to happen. After all, if Sun didn't open up Java, someone -- probably IBM -- would have eventually ripped it out of their hands. To quote Eric Raymond, "you can have ubiquity or control, but not both." (Ok, so that's more like a paraphrase than an exact quote, but y'all get the gyst. And speaking of ESR, there's a cool interview here in which he talks about -- and predicts -- Sun's open sourcing of Java.)

    In short, it was either do it now or do it later for Sun. And it's better they do it now, when they can still look good, than later, when they'd end up just leaving a seriously bad taste in the mouth of thousands of developers. They're strapped for cash and just signed their soul over to the Borg. Might as well do SOMETHING worthwhile and good, rather than just be a giant flaming ball of gas for news.

  51. Re:Yeah, by IBM. by 0racle · · Score: 4, Insightful

    ...a significant popularity. You mean just like Mono, or WindowMaker, GNUStep, DragonFlyBSD? Its a miracle when any piece of software, no matter what it is or what license its under, becomes popular. Simply taking a closed or heavily guarded app or language, remember the specs and Java API's are there for anyone to read, and turning that into an OSS project is not going to make it more popular, but will make it a lot less useful to Sun. If Microsoft suddenly opened Windows tomorrow, would that make Windows magically better then it was today? Would you spend the time submitting patches to a system that you would have to give up to Microsoft?

    Java is Sun. While that probably doesn't mean all that much to most people, it does to Sun and everyone whose spent the time and money to certify there apps as J2EE Certified. Sun would have to be smoking some really good stuff to think that giving that up would be a good thing. Java and C were made for very different reasons, C was to be the prefered language for Unix development, so it was stupid not to have it open and standardized as Unix went down the same path, Java was always concieved as something that Sun would keep, leverage it and open it enough that it would be used, but still Sun would have control.

    --
    "I use a Mac because I'm just better than you are."
  52. trolling for mono... by Kunta+Kinte · · Score: 4, Interesting
    From a business point of view, what's the point?

    Mono is nearing release 1.0 and is a very attractive platform for developers. Releasing Java open source 3 years ago would have screwed Microsoft hard, but now I'm not so sure.

    First you ask what's the point, from a business-point-of-view no less. Then you bring up the legal blackhole that is mono?

    The point is not basing your development on a technology owned by a ruthless competitor that has promised to squash you.

    The point is having a development environment that is equally supported on multiple platforms by the core designers themselves.

    The point is not to have the threat of patent suits looming over you for using an unauthorized and patented language/API/Runtime/Whatever-else-they-patented stack.

    If they GPL'd that as well, Sun might have a chance at getting a serious revenue stream happening.

    Oh yeah, the money just rolls in when companies GPL software, doesn't it.

    Ahhh... Only on Slashdot :)

    --
    Based on upvotes, Ageism is the only "-ism" Slashdotters care about and think isn't SJW
  53. Re:Yeah, by IBM. by glwtta · · Score: 4, Funny
    People run all kinds of Microsoft-made technologies and don't gripe.

    Uh? I thought the whole purpose of this site was to gripe about microsoft products.

    --
    sic transit gloria mundi
  54. Two corrections by SuperKendall · · Score: 4, Interesting

    3-In fact, there is actually LESS chance of fragmentation when Java lies in the hands of the public, first because it means that no one will start up a competing "openjava", a venture that would almost certainly lead to incompatibilities, and second because, as the example of the death of xfree86 shows, too much central and absolute control over software by a small group will inevitably anger developers and users alike, leading them to search for an alternative.

    Say, isn't "OpenJava" called .Net? Same difference to me, extremely similar platforms with huge amount of duplicated code (Ant and NAnt, JUnit and NUnit, etc.). What you said about the issues with forks is true until someone big enough does it, and we are seeing the result in front of our very eyes.

    As for control by the public - Java is already controlled by the public at large through the JCP. I do think opening the source could get some people more fired up about some things though, as the JCP can be rather slow.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  55. Tooth Fairy by RAMMS+EIN · · Score: 2, Insightful

    esr says:

    ``Anyone who believes a vendor is going to give away hardware under a contract that allows the customer to immediately strip off the software and repurpose it probably still hasn't faced the truth about the Tooth Fairy.''

    You mean that he does exist and wrote Linux, together with Santa Claus?

    --
    Please correct me if I got my facts wrong.
  56. Re:Good thing for FreeBSD by kwerle · · Score: 2, Interesting

    And in fact it is a nightmare if you want to deploy it on multiple FBSD boxes - and heaven forbid you want to sell a product that depends on it and make clients install it.

    Worst. Solution. Ever.

    (granted, it is a solution, but it sure blows)

  57. Good thought by Pecisk · · Score: 2, Insightful

    I guess it's a step forward, yeah, yeah, someone will say - it's not happened *YET*. BUT it could change certainly several things: 1) every distribution now could distribute JRE without any licensing issues - I guess it's first and main point about Java widespread on Linux boxes 2) Allow changes for others/forks - I guess second is rather risky, but I guess no one will fork Java unless it will be very necessary and pressing. I guess it could be done the same way it worked for Openoffice.org project - one project site, everyone can contribute, submit changes, Sun engineers do the rest. Yes, I guess most of you should understand that isn't that easy to open source Java - Sun clearly see beneficts, but legal team should figure everything out, everything must be sorted out, even code - I asume. So let's just wait for that. And yes, it is about god damned time - for people who don't want to use Mono because of fear from Microsoft.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
  58. Re:Yeah, by IBM. by cammoblammo · · Score: 3, Informative

    Umm, how are Linus and RMS like minded? Whilst they both support Freedom of software, they're completely different in their philosophies, ethics and favourite programming languages. Saying they're like minded is like saying that Microsoft and the Salvation Army are like minded because they both happen to produce goods and sell them.

    --

    Cogito, ergo sig.

  59. Re:Yeah, by IBM. by cammoblammo · · Score: 3, Informative

    Okay, I know, I'm getting off topic. But here's a link telling us how RMS views other FOSS advocates anyway.

    --

    Cogito, ergo sig.

  60. Re:No reason to open-source Sun's Java implementat by zerblat · · Score: 3, Interesting
    Java is not just a compiler. There already are free Java compilers and JVMs. The important part is the class library. Reimplementing all the classes and keeping compatible is a huge task (which GNU Classpath is working on).

    My point is, a free, forkable implementation of Java will happen -- with or without support from Sun. If free software people could use Sun's classes, the risk of having incompatible versions of Java (because of subtle differences in implementations or because some classes haven't been implemented yet) would be lower than it is now.

    Besides, having a complete and free Java environment perhaps could keep some free software developers away from C#/.Net

    --
    Please alter my pants as fashion dictates.
  61. Closed standards by jmorris42 · · Score: 4, Insightful

    > I disagree that "most" closed standards fall out of use. Many survive.

    Outside the IT world you have a point. But name ONE major IT standard that is still relevant that is a) closed and b) not a microsoft 'standard'. I exclude MS because they are a convicted monopolist and have certain unfair influences on the marketplace that has permitted them to maintain closed standards for a little longer than everyone else.

    Networking standards are the obvious example where closed has been the kiss of death. Closed information services were crushed by the Internet, all non-IP network protocols are now in legact maintaince mode. How many email systems are left other than SMTP/POP/IMAP? Instant messaging is the one holdout because Jabber couldn't get their act together to the point where every ISP became expected to host a Jabber locator server just like they host a mail/dns/news/etc server.

    File protocols are rapidly converting to open, with the notable exception of MIcrosoft and their Office formats. A host of closed graphics formats fell to GIF, JPEG and PNG. The myriad audio and video formats have all but collapsed to WAV/MP3/MPEG/AVI/WMV/OGG. Even the MS standards are fairly open (for MS tech) with the exception of rights restricted flavors of WMV. MP3 and MPEG are artifacts of a day when RAND licensing was considered open.

    JAVA must open or face a decline. It is the only current language with any real restrictions on implementations. Anyone is free to write a C compiler, and many do in school. Anyone if free to rewrite Perl, but would be daft to try. :) JAVA is the only language with a corporation full of lawyers threatening to sue anyone who releases an implementation they don't like.

    Even worse, with the current situation Linux distributors can't include a JVM (Sun's or IBM's) in their collection, even those who are willing to bundle closed apps, so no JAVA app can ever be a core app in the Linux or BSD worlds, and considering the state of affairs in Windows land it isn't likely to happen there either. That Sun can't see that widespread, unfettered distribution of the runtime is a plus for all Java advocates doesn't bode well for a real Open Source release of the JDK.

    But anyway, JAVA the language probably has a future but JAVA the emulator/VM really doesn't. Sun can slow the evolution down through skilled lawyering but native compilation similar to what GCC is now doing is the future, one where JAVA is just another language and source gets compiled to native code and depends on the normal system libraries.

    The only reason for the emulator was to allow closed source apps to be semi portable, but as closed source becomes less of an issue there will be less and less reason to pay the emulation penalty of the JVM. In the Open Source world portability is achieved with GNU autoconf, not by compiling all code to run on a mythical platform which is then emulated on whatever host it happens to be running on today.

    --
    Democrat delenda est
  62. Forking JAVA by jmorris42 · · Score: 3, Insightful

    > I think they're worried about someone forking it.

    Oh bull. How many incompatible forks of C++ are there? Not all compilers implement all of the latest ANSI standard but are all working toward compliance as fast as they can lest they lose relevence in the marketplace. Ok, how about Perl? It has been GPL from the start of it's life and there has been exactly ZERO forks. Python? Nope, no evil forks there. How about the granddaddy of them all, C? Yes, but the ANSI standard keeps pulling them all back into line, so it hasn't been a problem. Every time C shows its age the compiler writers start innovating and the good ideas get standaridized.

    Sun is still trying to think of a way to make JAVA a cash cow and is afraid that if they Open Source it that when they have the "Ah Ha!" moment that it won'y work because they opened it.

    And anyway, the idea of compile once, emulate everywhere is not exactly a great one if you live in the OS/FS world. Won't bother me a bit when Java becomes just another language that GCC compiles to native code and it's bundled libraries are sitting in /usr/lib with the rest. When programmers decide whether to use the bundled crossplatform graphic toolkit or use java bindings to Win32/Qt/Gtk/wxWindows/SDL/etc. When Python programmers are deciding whether to use Tk or Swing. Or in a bumper sticker size phrase, when Java is just another OO language instead of a religion.

    --
    Democrat delenda est
    1. Re:Forking JAVA by TheRaven64 · · Score: 2, Insightful
      How many incompatible forks of C++ are there?

      Not a good example. The language is the easy bit, it's the standard libs that are important. How many libcs are there? Have you ever tried moving code between glibc, BSD libc and msvcrt (the libc used by Windows)? All of them have slight incompatibilities which require (often minor) changes, and the C standard library is several orders of magnitude less complex than the J2SE class libraries.

      --
      I am TheRaven on Soylent News
  63. Re:It will be beneficial to Java in the long term. by Dj · · Score: 4, Insightful

    So you've gone and confused generics with autoboxing. And we're supposed to listen to you demand someone does templates. Uhuh.

    --
    "You know you want me baby!" - Crow T Robot
  64. Is this now the standard plan? by noldrin · · Score: 2, Insightful
    1. Wait for a product to be hovering near death's door
    2. Release product under a new restrictive open source license
    3. People complain about license
    4. Rerelease it under the GPL
    5. Programers spend a year making the code worthwhile
    6. People complains about how poor the opensource developement model works
    7. Really cool product emerges too late to make a big impact in the market at large.

    I don't mean to sound ungrateful.. but perhaps it would be smarter for companies to use open source earlier on, not as a last ditch effort. Java has been pigeoned holed as a very large plug-in for web browsers, which Flash has done a lot better with. If they are going to see Java as a big application platform, open source is necessary and not as optional.

  65. Re:It will be beneficial to Java in the long term. by StrawberryFrog · · Score: 5, Insightful

    There are various implementations of Java with truly good enhancements, like real templates, design-by-contract and other good stuff

    There are two dangers to this:

    1) Incompatible forks. Java is supposed to be "write once, run anywhere". Different implementations of a common standard can be good. Diverging language features can't be.

    2) At heart (without the class libraries) Java is still a small, simple, clean, readable, easy to learn language. Enough well-meaning enhancements, and it could end up looking like perl. Ugg.

    --

    My Karma: ran over your Dogma
    StrawberryFrog

  66. QT license by MysteriousMystery · · Score: 3, Interesting

    A QT style license that requires purchasing tools and rights from Sun for commercial use, while allowing free software (under an acceptable license) to be developed for free would be the best idea in my opinion. I'm sure there will be great debate at Sun over how profitable this will be, but in the long run this is definitely the way to go.

  67. Re:Reason to use Java? by nagora · · Score: 2, Interesting

    Python is at least as portable for all practical needs,

    I'm not really a fan of either language but I would say that I've yet to see a Windows machine with Python installed on it while it's been years since I saw one without Java. For web-based applications I would imagine this is a big deal.

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  68. Re:Yeah, by IBM. by cozziewozzie · · Score: 3, Informative

    Actually, the Java Desktop is a Linux distro running GNOME. That's the only GPL part there is (and it has no connection to Java other than coming with a Java VM).

  69. Re:Good thing for FreeBSD by Baki · · Score: 2, Informative

    Why? Just create the package on one of your FBSD boxes (including downloading source manually etc), then pkg_install the resulting package on all of your FBSD boxes.

  70. Why the hatred against our ally?!? by Baki · · Score: 4, Insightful

    Why do I sense so much hatred and ungrattitude against SUN? It has been one of the pillars of UNIX, has given away many technologies that today define UNIX/Linux. Without SUN UNIX would have been irrelevant long ago, and with it Linux would have been just as irrelevant.

    Why don't people see the strategic importance of the UNIX world (which includes Linux) holding together and fight against the real enemy?

    I do have my concenrs regarding Suns recent "peace" with the enemy, maybe we can no longer rely on SUN, but at least one must acknowledge what SUN has done for the UNIX community.

    The lack of historical perspective and irrationalism of many of the SUN haters is shocking to me. It almost makes me think that the enemy has sent inflitrators on slashdot with the purpose to spread division and internal struggle inside the UNIX world.

    1. Re:Why the hatred against our ally?!? by zander · · Score: 3, Insightful

      Why do I sense so much hatred and ungrattitude against SUN?

      Suns past has kept it out of trouble from many for quite some time, but like most companies also do; its time to re-evaluate their commitment. And Sun is not giving enough to make Java grow the way it can. All these people are not asking Sun to give more, they are asking Sun to let their child out in the open where it will interact with others and gain new experiences.

      Right now Sun is limiting the growth of Java more then stimulating it. All the kids on the block see it, but like any parent the last one to see it is Sun itself.

      There is no hatred; just frustration.

  71. An example of hybrid-source by minkwe · · Score: 3, Insightful
    A casual look at their statements reveals their minds.

    In this article in which they promise opening up Solaris, They say:

    "Look, you only need to look at what we've done with Java to understand how Sun views the value of incorporating community feedback," he said. "Java could not exist if only Sun is supporting it. It exists because there are hundreds and thousands of partners. We need to now take the model with Java and bring it to Solaris."

    The uninformed on-lookers will only see the statement "Sun warms to open-source for Solaris" which gives them more points.

    Next concerning Java, a few months ago they said,

    "Schwartz also noted that people who stick to Sun's licensing terms and maintain compatibility with Sun standards can have access to the Java source code. Changing the licensing to an open-source model would encourage different implementations, he said."

    Now they are saying:

    "We haven't worked out how to open-source Java -- but at some point it will happen," Srinivas said. However, he noted "it might be today, tomorrow or two years down the road".

    Again, the uninformed on-lookers will only see the statement "Sun to open-source Java" which gives them more points.
    Summary: They promised to make Solaris become like Java, meanwhile they don't know if at all Java will be open-sourced in this lifetime.

    This is what is called hybrid-source: A vapor version of open-source meant only to gain favor with the open-source community and the business world without any active steps or concrete plans to put it in effect.

    --
    "Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
  72. No, not the GPL by Aapje · · Score: 5, Informative

    The shitstorms are because Die-Hard Linux geeks/distros want to have everything on their computer/CDs under the GPL.

    I don't believe you. Do those distros ship without Perl and Apache, which are both not GPL licensed?

    IF they release it under the GPL, I see this making the open-source world a lot friendlier to Java.

    Open-source != Free. A significant group of people prefers a BSD-like license over the GPL. A GPL-compatible BSD-like license will be usable by both GPL and non-GPL programmers. Most programming language implementations do not use the GPL, and that is probably for a good reason:

    Python - BSD-like license
    Perl - Artistic
    Gcc - GPL (but glibc is LGPL!)
    Zope - BSD-like
    Php - BSD-like
    Scheme - BSD-like
    Ada - Artistic
    Eiffel - BSD-like
    TCL/TK - BSD-like

    Furthermore, the GPL may be a serious problem for Sun. Not all Java code is necessarily copyrighted by them. They might have licensed some code from others. With a BSD-like license, they can just keep those parts with their original license. A GPLed Java would require relicensing, which Sun cannot do. Another problem may be patents. Sun owns quite a few Java-related patents and the GPL requires them to give everyone a free license to those patents. That would allow MS to use those patents in their software and even to build another evil Java clone, but then, Sun wouldn't be able to do anything about it. Another patent problem may be that third party patents cannot be used in GPLed software (even though Sun can license it). So Sun might not be able to include some functionality in a GPLed Java.

    --

    The Drowned and the Saved - Primo Levi
    1. Re:No, not the GPL by dnoyeb · · Score: 3, Insightful

      Furthermore, the GPL may be a serious problem for Sun. Not all Java code is necessarily copyrighted by them.

      You are aware that Java is not written in Java? One issue is open sourcing the Runtime Enviornment source code which is java code, the other issue is opening the Virtual Machine which is not. Everyone has been griping about the VM code.

  73. Re:Yeah, by IBM. by AnyoneEB · · Score: 4, Informative

    Which is great until you want to have a GUI. Although it's being worked on, GNU Classpath doesn't really support Swing. Of course, it sounds like mostly Java is used for non-graphical programs anyway, but not always. Open-sourcing Java would mean that it could be included by distros and used for desktop apps.

    --
    Centralization breaks the internet.
  74. What's the fuss by Second_Derivative · · Score: 2, Interesting

    The Java spec and compatibility will be diluted? Surely trademark law was designed to prevent this very problem.

    I dunno if Java is a trademark or not, but either with a trademark or a license clause in the distribution, Sun could require that any derivative product that does not conform to the Java spec may not use the word "Java" in its name or in any promotional literature (kinda like a saner version of the BSD advertising clause).

    I can't imagine Sun actually depends on the technical specification as a significant revenue source. People despise Microsoft these days more than ever and don't much care to be locked into their .NET system which has just one lord who can force you further along the upgrade treadmill at a whim. Sun putting their money where their mouth is and truly making an open Java implementation available could be just what it needs.

    (Come to think of it the spec already is pretty much 'open' thanks to the JCP. So you have to pay Sun for a copy of the spec. You have to pay ISO or ANSI or whoever to the C and C++ specs too ... right?)

  75. Autoconf? by Roy+Ward · · Score: 3, Insightful

    > In the Open Source world portability is achieved with GNU autoconf, not by compiling all code to run on a mythical platform which is then emulated on whatever host it happens to be running on today.

    Um, which platform do you use - it wouldn't be Linux x86 which pretty much all gnu software has already been ported to would it? Autoconf is good at getting things mostly right, but there are still various tweaks to get something running on a platform it hasn't been built for before (I know ... I've spent days over such porting).

    All the Java I've written seems to run fine without modification under MacOSX, Linux, FreeBSD, Solaris ...

    If autoconf is the route to native portability, I think I'll stick with the current JVM model and get some work done, thanks you.

  76. In other news... by hardgeus · · Score: 4, Funny

    Yeah, baby. I'm going to divorce her and marry you. Just keep sleeping with me.

  77. Java will be open source! Never! Sometime! by rtos · · Score: 3, Insightful
    This is interesting, because just three months ago McNealy said there was no way they would open the Java source:
    "Despite urging from competitors and open source advocates, Sun Microsystems Inc. of Santa Clara, Calif., will not open the source to its Java programming language anytime soon, said Sun CEO Scott McNealy during a news conference at the 2004 FOSE conference. "We're trying to understand what problem does it solve that is not already solved," McNealy said."
    One day he wears a silly penguin suit and the next day he says that Linux is "great environment for the hobbyist" but not for corporate IT shops. One day he says there's no way they are going to open source Java, and then they announce that they will.

    If I didn't know better, it would seem that Sun is flailing pretty badly at this point.

    --
    -- null
  78. Re:sun's stock - racing to zero value by Decaff · · Score: 2, Insightful

    Sun has no real value except for the ongoing license revenue from solaris hardware and software.

    That's a very big 'except for'. Also, Sun now make a considerable amount of money from selling software services. Oh, and by the way, its 'Sparc' hardware. Solaris is an 'Operating System'.

    Linux did its job and forced them into only high end servers

    Funny, I thought Open Source was about the pleasure of writing quality code, comradeship between developers, and providing choice. I did not realise it was designed specifically to annoy Sun.

    where there is
    - much less demand


    There is?

    - much stronger competition

    But I thought you said that Linux was competition at the low end. How could Sun have been supposedly forced into 'only high end servers' without competition?

    - commodity high end hardware

    So?

    - 'portable' dbms systems - Oracle 9 data is the same on aix, solaris, hp, etc

    And has always been. Sun have always supported portability. That's why they went for UNIX decades ago and not a proprietary closed system like IBM and HP used to have. Sun got there first. When they started with UNIX, they published open standards for everyone to use, such as NFS. They allowed other manufacturers to use their Sparc designs. Sun realised that competition and portability are good: it means that competitors software can run on your systems.

  79. Re:Yeah, by IBM. by Decaff · · Score: 2, Insightful

    no connection to Java other than coming with a Java VM

    And Sun Studio Java development tools.
    And Mozilla with full modern applet support.
    And Java security tools.
    And Java integration with Star Office to allow database connections and Office component development.

    By the same reasoning Java Desktop has no connection to Linux other than including Linux...

  80. Re:Yeah, by IBM. by Decaff · · Score: 4, Insightful

    Well, i'm not sure how sun is making a ton of money off of java now.

    They do it by selling software services.

    Sun: "We'll sell you software stuff and services."
    Customer: "OK - what will it be written in?"
    Sun: "Java"
    Customer: "Cool - we already use java, its free, and we can use your software anywhere."

  81. "Open Source" in Suns dictionary... by hingo · · Score: 2

    We should remember that when you read all the "we might Open Source Solaris" articles we've seen, what they are talking about has nothing to do with Open Source as we know it. At best it is some kind of Microsoft Shared Source scenario, but probably it's just smoke and mirrors. Remember, Suns major partners this year have been SCO and Microsoft.

    So when they now say they might "Open Source" Java, I don't see any reason for ESR or RMS (or anyone else for that matter) to get excited.

  82. Open License too? by Kainaw · · Score: 2, Interesting

    Open Source is nice, but not necessary for most Java users. How many Java programmers are complaining, "Man, I could write the program I want to write if I could just change the source code for Java!" However, an Open License would be great. The primary drawback to writing a program in Java is that the runtime engine has to compile the program on the fly. There are programs to compile the program for specific operating systems, but they are required to inculde the entire Java runtime library set due to licensing restrictions. So, if you don't use something like port IO or Swing graphics in your program, it has to still be included in the executable. An open license would allow a Java programmer to compile an executable that is small and fast and generally competitive with a similar C/C++ program. That solves the complaint that I normally hear from Java programmers: "I could write that in Java, but who would use it since they have to figure out how to install the runtime engine, get the classpaths configured, and then open a command prompt or teach their system to figure out a .class file should be run by Java?"

    --
    The previous comment is purposely vague and generalized, but all of the facts are completely true.
  83. GCJ - SWT Gui by orasio · · Score: 3, Informative

    Create native, cross-platform GUI applications

    Create native, cross-platform GUI applications, revisited

    Not compile once, run everywhere, maybe write once, compile everywhere, but that is Java, GPLd with a GUI.

  84. Re:Yeah, by IBM. by Marcus+Green · · Score: 2, Insightful

    I believe It would be possible to use the Sun Java Desktop without using any Java. You could ignore the Java development tools, use Mozilla without accessing any applets, use StarOffice without accessing a database (which is probably how most people use it at the moment) and I am not aware of the Java security tools. Can anyone comment on how vital these Java security tools are to the system?

    Now by contrast how much of the Sun Java Desktop would work without the Linux kernel, the associated GNU tools and GPL'd software?

  85. This Reminds me of C by jmac880n · · Score: 2, Insightful

    Sun's situation with Java is really reminiscent of AT&T's situation with Unix and C.

    One could make a good argument that the excellent portability of C is because of AT&T retaining tight control of it for so many years. Many people learned the language and there were many applications written for it, so by the time more compilers were written for it, and later, when it was standardized, no one wanted to break anything.

    In other words, the existing mass of programs keeps C stable and reasonable. If language changes different enough (or innovative enough) come along, they are put into a new language derived from C, and given a new name (like "C++" or "Java").

    Is Java at that point now? Is there a big enough mass of Java code out there to keep the language stable without Sun's help?

  86. Re:McNealy says THEY WILL NOT open the source by qqqqarl · · Score: 2, Informative

    Friday 4th June 2004

    Sun's Scott McNealy squashes idea of Java becoming open source
    [PC Pro] 13:07

    Sun's CEO Scott McNealy has squashed hopes that its Java programming language could be made open source, and cast a shadow over Sun COO Jonathan Schwartz's statement yesterday that the Solaris operating system was to go the same way.

    At a news conference during the public sector technology showcase FOSE 2004, McNealy said he couldn't understand how open sourcing Java would solve anything.

    In February, Eric Raymond, President of the Open Source Initiative, published an open letter to Sun in which he called on Sun to make its Java platform Open Source, describing the company's Open Source strategy as 'spotty' and 'confused'. IBM also published an open letter to Sun with a similar plea.

    At a UK conference in March, McNealy joked of such letters: 'They do get looked at. Sometimes with a chuckle.' His comments on demands to open source Java then echoed those he gave at FOSE. 'I don't know what problem that would solve apart from IBM's childhood envy,' he said.

    Java is an object-oriented programming language designed to allow the same version of a program to run on multiple platforms without modification by using a Java runtime environment that sits between the Java program and the operating system. Java is the jewel in Sun's crown, as far as McNealy is concerned, because of its pervasiveness. 'There's not one other platform where you can write to it no matter whether it's a cell-phone or the Mars rover,' he said. On rivalries between Java and Microsoft's .Net he said: 'Mankind won, Microsoft lost.'

    Sun maintains that open standards are more important and that it has to retain control over the direction of Java to prevent the creation of different implementations that may be incompatible - something Sun accuses Red Hat of having done with its version of the Linux-based operating system.

    This doesn't bode well for the chances of open-sourcing Sun's Solaris operating system. While speaking at the SunNetwork confe

    ADVERTISEMENT

    rence in Shanghai, China, Schwartz commented: 'I don't want to say when that will happen... But make no mistake - we will open source Solaris.'

    However, he said this would be done in the same way that Sun holds stewardship over the direction of Java, which will frustrate many in the open source community.

    However, Sun is not entirely against an open source version of Java. It has indicated in the past that it might be possible to relinquish its stewardship position to a neutral governing body that would assure open-source implementations wouldn't 'fork'.

    And Sun isn't the only company with the skills to create an open source version of Java. Sun's Chief Technology Evangelist, Simon Phipps, told us in a recent interview: 'Why has no-one else offered to create an Open Source version of Java? Maybe because it's on the 'too hard' list. Sun would support an Open Source version of Java, but it needs a lot of money and time to do so. You can't just flick a switch. Right now Sun has higher priorities in the form of Java 1.5.'

    Despite the rhetoric, it doesn't look as if open source implementations of either Java or Solaris will be around any time soon.