Slashdot Mirror


FreeBSD Foundation Announces Java License for Free

nt2UNIX writes: "There is an article on Daily Daemon News that the FreeBSD Foundation has announced the inclusion of a FreeBSD native SUN Java SDK and RunTime Environment for the January 2002 release of FreeBSD 4.5 The whole announcement can be found here."

12 of 137 comments (clear)

  1. Too bad the licensing blew it by freebsd+guy · · Score: 5, Interesting
    As a former FreeBSD committer, I worked extensively with the team that produced the JRE/JDK project. Since programming languages can only be protected by patents (not copyrights), our original intention was to craft a clean-room version of Java that we could release under the BSD license, just like everything else in our distribution. Unfortunately, manpower was tight, and we were not able to do it all on our own. Hence, we discussed the matter with Sun and (IMHO) compromised our principles (unrestricted distribution in source and binary forms) in order to get the project done.

    Our experience should serve as an important lesson to open source developers who try to tackle too large a project by themselves: do not sell your soul to Corporate America. Sure, we have a native JRE/JDK, but the only advantage is that it is native - not Free in any stretch of the imagination. (Not even restricted-Free, e.g. GPL).

    All that aside, I have been testing several snapshots of the Java tools and they are very responsive and stable. More so, I am afraid, than Blackdown - although the ultimate test will be to see how it compares with the JRE running on a Solaris/SPARC machine.

    freebsd guy

    1. Re:Too bad the licensing blew it by Metrol · · Score: 5, Insightful

      Hence, we discussed the matter with Sun and (IMHO) compromised our principles (unrestricted distribution in source and binary forms) in order to get the project done.

      Certainly a fully open and free version of Java would have been preferrable and all. Even still, is this really that much different then having the Netscape 4.x browser included? For years this has gone along with both Linux and FreeBSD to provide what the community couldn't, a functioning browser.

      Just because Netscape provided a browser didn't mean that work wasn't done to produce a more open product. The folks over at KDE stepped up to the plate and knocked one outta the park with Konqueror. And of course we now have Mozilla going pretty nicely. Two great apps displacing the closed source version that preceded it.

      All I'm getting at here is that Sun need not displace any and all efforts that might look to go into a JVM for FreeBSD. Maybe it fills the role needed for a couple of years until interest in doing a fresh version as you described gets enough going to actually make it happen.

      --
      The line must be drawn here. This far. No further.
  2. This is nice by metlin · · Score: 4, Insightful

    Since Microsoft is slowly trying to push third party development applications away from it's platform (apparently to make way for .NET), this is a good sign.

    I'm not a big fan of Java, but if there are enough number of viable platforms for development, I'm sure attention could be shifted from the Win* platform to other unices.

    FreeBSD is a very stable and robust platform, but to what extent has it managed to penetrate the existing MS market? Apparently Linux seems to be doing this, and the reason is not anything else, except support for existing applications.

    I'd like to see where this takes the FreeBSD marketshare.

  3. Java license for Free (as in ???) by GGardner · · Score: 4, Informative
    Well, it isn't free as in speech, cause we don't get source code, which means it is x86 only (amoung other issues).


    And the FreeBSD team had to pay $3k in legal fees to lawyers to wrangle licensing terms, so it is hardly free as in beer.

    1. Re:Java license for Free (as in ???) by Zillatron · · Score: 3, Funny
      Well, it isn't free as in speech, cause we don't get source code, which means it is x86 only (amoung other issues).

      It's O.K. for it to run on x86 only. The focus of FreeBSD is to run as well as possible on x86 machines. If you want to run on other architectures, try NetBSD whose motto is ``Of course it runs NetBSD.''

    2. Re:Java license for Free (as in ???) by Derkec · · Score: 3, Insightful
      And the FreeBSD team had to pay $3k in legal fees to lawyers to wrangle licensing terms, so it is hardly free as in beer.


      Um.. Nobody held a gun to their head and made them hire lawyers. Sun, who built and owns the IP, graciously let them use it Free as in Beer. While I know everyone who codes should give away all their source out of the kindness of their hearts, the for slimy corportate types the folks at Sun are being pretty decent towards a group improving a competing Unix OS.

  4. This is huge by astrashe · · Score: 3, Interesting

    I love it -- the lack of solid java support is the biggest problem I have with FreeBSD.

    Now if only the same thing would happen with OpenBSD -- we could write tomcat based web apps, and wouldn't have to worry so much about being hacked.

  5. Hm... don't know. by burtonator · · Score: 4, Interesting

    I am a big fan of Java. I think my accomplishments speak for themselves. I have done a lot of work under Jakarta and founded two of its core projects.

    That said. I am very upset at what SUN has done to systematically *destroy* Java's potential.

    In 1995 everything was great, Java was going to change the world.

    Then they decided to play games, they pulled out of the standards committees and now there will be no ECMA or IEEE standard for Java.

    Not only that but they have shown that they have NO interest in EVER Open Sourcing Java.

    Every new Java specification is dumped into the JVM as proprietary code.

    I mean I can understand that Open Sourcing a large proprietary product like Java can be hard. Good examples are the Mozilla and Tomcat projects. Proptietary products can end up using libraries that you don't have the license too. Not only that but you have to get sign off from all the morons that think proprietary is the only way to go.

    But SUN *continues* to dump code into the proprietary JVM making it bigger and more bloated than ever before.

    In case Some of you don't know, SUNs MO for extending the VM is to work on a dedicated sub-project outside of the VM and then getting it targeted for the next revision.

    So for example JSSE (Java Secure Socket Extension). This is a external library that can just be plugged into any VM. Instead of releasing this as an external project that has different licensing they just dump it into JDK 1.4 with the same old stupid non-OSS license.

    THIS IS NOT THE WAY TO DO IT SUN!

    I think it is great that FreeBSD can now distribute the JDK.

    It just seems too little too late for me.

    Java has real competition now. They are not the ONLY game on the block.

    Python and C# are going to give you a REAL run for your money SUN.

    So, they way I see it, you have two options:

    1. Loose. C# is an IEEE standard as well as the CLR. When mono is successful no one is going to want to use your proprietary JVM anymore.

    2. *WIN* Open Source license the JVM. Yes... I know it is scarry but this is you ONLY choice. Java still has a lot of great momentum. (*cough* Jakarta *cough*)

    Clearly you aren't interested in the standards process, this is fine. I can't blame you. Standards are not a panacea! Nice to have but not really a requirement.

    So just BSD license it and be over with it. MS isn't going to steal it! They aren't interested in Java anymore.

    What? Aren't going to Open Source Java?

    Fine. I am just going to use C#.

    Sorry if this seemed like a troll. I am just sick of these stupid games :(

    I just want to change the world. Is that so bad :)

    1. Re:Hm... don't know. by markj02 · · Score: 5, Insightful
      C# is an IEEE standard as well as the CLR. When mono is successful no one is going to want to use your proprietary JVM anymore.

      Well, first of all, AFAIK, C# is an ECMA standard, not IEEE. Now, I don't get your complaint. You say that there is a problem with Sun "dumping proprietary libraries" into the Java spec. But the Java language, JVM, and core libraries are as-well specified as C#/CLR, and they are stable. Beyond the core ECMA specs, Microsoft is completely proprietary, with NO free implementation at all and NO decent specs. And there is no guarantee that Microsoft will even stick to their spec--they will likely extend the hell out of what they submitted as a standard. Sun at least writes pretty good specs for what goes into new releases of the Java platform and they give you a free implementation.

      When mono is successful no one is going to want to use your proprietary JVM anymore.

      Why would anybody care about Mono? It's going to use non-standard APIs on a little-used platform.

      2. *WIN* Open Source license the JVM. Yes... I know it is scarry but this is you ONLY choice. Java still has a lot of great momentum. (*cough* Jakarta *cough*)

      That makes no sense either. Why do you care about open sourcing Sun's JDK? Implementing C#/CLR as part of Mono is at least as hard as implementing Java/JVM. Yet, you seem convinced that Mono will be successful. Well, if the Mono people can hack up C#/CLR, why does it matter whether Sun open sources Java/JVM? Why can't someone else just implement a high-performance Java/JVM? And what has Microsoft done for the open source community later? Ever?

      Sun makes available a great implementation under usable license terms. If you want something open source, rather than whining and stomping your foot that they aren't giving you more, go implement your own. Sun has already given you more than Microsoft likely ever will.

      And, in fact, the equivalent of C#/CLR/CLI already exists for Java in open source form in the form of several open source Java compilers, the Intel ORP, and open source libraries. If that functionality is what you or the Mono project are after, you could have had that years ago.

    2. Re:Hm... don't know. by rusti999 · · Score: 3, Informative

      Make a clear distinction between specification and implementation. Sun has made the specification for Java open for all to see. JDK is an implementation of the Java platform that happens to be written at Sun. By no means this is the only way to develop and use Java. For instance, you can grab Jikes compiler, compile your Java program, and run it on Jalapeno VM. You are even allowed to write your own implementation of the compiler and the VM. One catch is, if you want your implementation to be certified as 100% Pure Java, you need to pass the Java Compatibility Kit (JCK), which you need to license from Sun.

    3. Re:Hm... don't know. by macpeep · · Score: 3, Interesting

      "But SUN *continues* to dump code into the proprietary JVM making it bigger and more bloated than ever before."

      Not into the VM. Into the core API. There's a HUGE difference. Of course the two walk kinda hand in hand but that's like saying KDE and Gnome are in the Linux kernel.

      "Java has real competition now. They are not the ONLY game on the block. Python and C# are going to give you a REAL run for your money SUN."

      Umm, C# yes! Python, I don't think so!! Some other people would say Perl, but seriously, they are not in the same league if you talk about industry wide acceptance. C# and .NET will definitely give Java a run for their money though!

      I don't see how being an IEEE standard has any direct correlation with success or failure of a language though. Visual Basic is not a standard of any kind and it's one of the most used programming languages / systems out there. Java is also hugely popular and is also not a standard. JavaScript hasn't become any more or less popular after ECMA made it a standard ("ECMA script"). Or if it's more used now, it's not because web designers would go "oh! it's an ECMA standard!". The list goes on with other technologies too.. Flash (as in web animations) for example.

      "So, they way I see it, you have two options:"
      [snip]
      "2. *WIN* Open Source license the JVM. Yes... I know it is scarry but this is you ONLY choice."

      Time to wake up! Java is doing just fine and even if Sun doesn't have a totally optimal strategy with it, you're living in la-la land if you seriously think that open source licensing the JVM is Sun's "only choice" (you even spelled only in all-caps!). The community process is working fine and Java is just getting wider adoption and acceptance every day. Most new cellular phones that are going to be released in Asia and Europe during 2002 and onwards will come with a JVM built in. More and more web servers and application servers run Java.

      Open sourcing Mozilla did dick all for Netscape. Sure, it is going to produce a nice browser a year from now (five years down the road) when Mozilla completes, but as far as grabbing back market share and battling the competition, it has failed miserably. Check the logs of any major "neutral" web site and you'll see that Mozilla has completely marginal adoption. Neutral here means such sites where the main users aren't gear heads.

      "Fine. I am just going to use C#."

      I saw similar reactions when Microsoft came out with J++. People paniced, accused Sun of "destroying Java" and predicting that Java would be dead within a year, replaced by "Microsoft Java". This was around 1997 or 1998 or so.. Don't remember when exactly. Lots of people were talking about jumping ship. I guess it just goes to show that Sun and the Java developer community might have more of a clue than you think.

    4. Re:Hm... don't know. by peter+hoffman · · Score: 3, Informative
      It has been SUBMITTED to the ECMA (not IEEE), but I'd like to see link to info that it actually has been APPROVED as a standard. The last spec document I saw had the entire chapter on exceptions missing, for instance.

      The difference between submitted and approved is an important point so I checked for the current status at ECMA where the NEWS link on the front page led to this:

      Assembly met in Montreux on 112the December 2001, and approved 33 revised and 7 new Standards. Among the new Standards, the files of Standard ECMA-334, C# Language Specification, and Standard ECMA-335, Common Language Infrastructure (CLI), are already available in this web site and can be freely downloaded.

      An ECMA TR, ECMA TR/84, related to Standard ECMA-335, has also been approved and can be found here.