Slashdot Mirror


FSF, OpenOffice.org Team Reach Agreement on Java

Bruce Byfield points out his NewsForge (part of OSTG) article about something good coming out of the conflict over Java in OpenOffice.org. It begins "A dispute between the Free Software Foundation (FSF) and OpenOffice.org (OOo) over the increased use of Java in the upcoming version 2.0 release of OOo is over -- at least for now. The two groups have found a short-term solution, and are working together on ways to keep the dispute from happening again." The story provides a decent background on why it matters, and shows a surprisingly conciliatory attitude on both sides.

79 of 411 comments (clear)

  1. Will this always happen. by jellomizer · · Score: 4, Insightful

    Will this always happen when a product reached the popular user base? I think there should be more work to integrating OSS project with Non OSS projects. Either making Non-OSS projects with OSS Prerequisite and vice versa. If OSS it is about freedom, why do they make it difficult for us to choose a non free development method? If you become to popular then you will be forced to use OSS tools except for what the developers think is the best tool for the job. We should be able to develop without the Free Software Organizations Pressuring us to make our legally developed products fit their idea on what is Free Software. If this is played out to the full extent then we are just as stuck as those who choose to use non-OSS products because we are forced to choose between what is available OSS. I believe in freedom as me as a developer to allowed to choose what tools I wish to use, and for other to assume that I have weighed the Pros and Cons of my choices. This type of stuff that happens is why commercial companies are weary of OSS.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Will this always happen. by ZephyrXero · · Score: 5, Interesting

      This stuff happens because you shouldn't build open/free software off proprietary software. If you want to use open software as a foundation or library for your proprietary software, that's fine...but you don't develop open source code with a closed source language. It defeats the purpose of it being open. Linus found out the hardway and I'm glad that Open Office will hopefully be having an easier time...

      --
      "A truly wise man realizes he knows nothing."
    2. Re:Will this always happen. by FidelCatsro · · Score: 2, Insightful

      the problem i belive was that OO.org was origionaly star office (star office still being around and being the comercial version of OO.org basicaly now)and the code base was heavily tied to java already .Sun had decided to open the projects to get some input from the oss world in exchange for an open source office program.
      So it is only natural that they would be still using alot of java , not that i agree entierly with the decision to continue to build upon the java elements but just a little background as to why it hapens

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    3. Re:Will this always happen. by davecb · · Score: 5, Insightful
      ZephyrXero writes: don't develop open source code with a closed source language.

      Remember the bad old days when the brand-new language "C" was owned by Bell Labs, and they claimed anything you wrote in C belonged to Bell?

      Remember how long that was true? As measured in picoseconds?

      There are no closed source languages. That's an urban legend. You can try to booby-trap a language, like MS tried to do to Java, but that won't work, either. You may recollect that MS failed in that effort, expensively(!).

      It's almost impossible to encumber open source software by using proprietary tools. That's a self-serving tale told by the proprietary vendors, and false.

      --
      davecb@spamcop.net
    4. Re:Will this always happen. by Tim+C · · Score: 2, Insightful

      you don't develop open source code with a closed source language. It defeats the purpose of it being open. Linus found out the hardway

      Linus used Java in the kernel?! There I was thinking it was getting faster, and it was because he was rewriting Java code in C all along!

      Seriously, the BitKeeper debate has nothing to do with this. He was given a free licence, which was then revoked, as was allowed by the terms of the licence. How is that like Java? If Sun went belly-up tomorrow and/or abandoned Java, I still have my current JVM installs and permission to use them.

    5. Re:Will this always happen. by Jason+Earl · · Score: 4, Insightful

      The folks at Sun did get to choose the tools, that's why they used Java. If the Free Software Foundation had chosen the tools then OO.org would probably use guile or some other Free Software tool.

      The problem, of course, is that OO.org's new Java stuff didn't work with any of the Free Software JVMs. Now, that may not seem like a problem to you, but that's precisely the sort of thing that gets the folks at the Free Software Foundation worked up. So what did the FSF do? It looked into forking the OO.org code and replacing the Java dependencies with Free Software. The FSF hackers wanted a version of OO.org that they could use on a completely Free system, and they were willing to put in the work to make such a beast happen. The folks at Sun have a long history of dealing with the FSF, and they knew that the last thing that they wanted to see was a Java-free FSF fork of OO.org that would draw potential hackers away from their codebase. This is especially true considering the fact that distributions like Red Hat (and Fedora), Debian, and many others would almost certainly use the Free Software fork of OO.org by default. So Sun offered to cooperate more with the hackers working on running OO.org on gcj.

      That's nothing more than straightforward diplomacy. Neither side got what they really wanted, but it was close enough that the two sides are willing to work together. The FSF would much rather have gcj be the default Java for OO.org, and it would like to see the documentation and everything else reflect the use of gcj and not Sun's proprietary Java, but that's not what the FSF is going to get. What the FSF is going to get is that Sun is going to include fixes that will allow you to use gcj into the main branch of OO.org. My guess is that Sun is going to do just enough for the FSF so that it isn't tempted to fork OO.org.

      Personally, I am glad that the two groups worked things out. However, if they hadn't worked things out I would probably have used the FSF branch of OO.org simply because that's what Debian would be able to put into main. Debian's packaging system has spoiled me so badly that I now hate having to manage software myself.

    6. Re:Will this always happen. by jimicus · · Score: 5, Insightful

      He was given a free licence, which was then revoked, as was allowed by the terms of the licence. How is that like Java?

      The concern was that OO.o was using proprietary extensions to Java which aren't well documented and are exclusive to Sun.

      That being the case, Sun going belly-up isn't the issue. Sun going all SCO and announcing that from now on anything using their version of Java will have to pay $699 for a license is.

    7. Re:Will this always happen. by Anonymous Coward · · Score: 5, Insightful

      The problem isn't the language, it's the libraries. Java, .NET, Perl, Python, Ruby, etc have complex standard libraries. This is expecially true for Java, which includes far more of the GUI system and other OS-specific features as part of the standard library.

      In essense, Java == C++ plus the C++ standard library plus Win32. It's simple to code portable C++ if you use only the C++ standard libraries, but the moment you start using Win32, you have a portability problem. Until something like WINElib makes the Win32 layer portable, any exclusive use of Win32 in a C++ project locks out Linux and other free OSes.

      That's the problem. GNU/CLASSPATH has made outstanding progress lately, but it hasn't yet reimplemented all the Java libraries. It'll take some time before it does. Until then, using functions/classes that are not implemented in GNU/CLASSPATH will be a problem for any open source software.

    8. Re:Will this always happen. by bladesjester · · Score: 2, Insightful

      There was, I though, a rather amusing part of someone else's argument further up the page.

      It's funny because it basically proves our point rather than supporting his:

      "The FSF doesn't care about the programmers, as long as the code remains free."

      Yes. Damn you and all of your lives as long as I get what *I* want. Sounds like Stallman.

      I've ranted on Stallman more times than I can count, and I don't think i could have put it better in a single sentence. The irony was that it came from a Stallman Supporter. =]

      Personally, I'd like to see the man tarred and feathered and then boiled in oil. I get so bloody tired of hearing his rants about "it may be free, but it's not Free"

      I wish he'd refuse to use *all* "Free" tools. Somehow I doubt that computer he uses was "Free".

      It'd be great. He'd be shut up to the point of being easy to ignore and we could actually get some work done without being called evil because we want to eat.

      --
      Everything I need to know I learned by killing smart people and eating their brains.
    9. Re:Will this always happen. by willCode4Beer.com · · Score: 2, Insightful

      interesting post but, I don't think it applies.
      Open Office started out as a proprietary product, not an open one. Its was later made open source.

      I guess we should throw away Apache Tomcat, JBoss, Ant, Jakarta Commons to name a few.

      Or maybe, when you build a project, you build it in whatever language you want. Its your project. If people don't like it, they don't have to use it.
      As for the OOo debate, I'm sure MS would be happy to sell an office suite to those who object so strongly to the use of Java in OO.

      --
      ----- If communism is a system where the government owns business, what do you call a system where business owns govern
    10. Re:Will this always happen. by sbrown123 · · Score: 5, Informative

      The Java API *is* well documented. The problem with the extensions is that the open source JVMs (GCJ in particular) did not handle them correctly. This is not a big deal. Someone should report the bugs with GCJ to the project's bugzilla -or- help fix GCJ to get it to work. This was the result of the conflict anyways:

      The FSF, Stallman explained, did not have a preference for other programming languages over Java. It simply wanted assurance that any Java code would be compatible with free implementations of Java. After discussion options with Carr, he suggested that the Free Software Foundation would concentrate on expanding the GCJ efforts

      Yep. Conflict solved. OO.o can stay free of Sun's JVM if it wishes and GCJ gets some bugs exorcised. Everyone wins.

    11. Re:Will this always happen. by blechx · · Score: 4, Insightful

      "to him BSD is not free"

      Yes it is, FSF lists the BSD licence as a free software license. Tho the original version has certain "flaws" that renders it incompatible with the GNU GPL.

      "What has Stallman done that's original thought"

      He like STARTED the whole free software movement, enough said imo.

      And of course he's a saint ;)
      http://www.gnu.org/people/saintignucius.jpg

    12. Re:Will this always happen. by kcbrown · · Score: 3, Insightful
      Remember the bad old days when the brand-new language "C" was owned by Bell Labs, and they claimed anything you wrote in C belonged to Bell?

      Remember how long that was true? As measured in picoseconds?

      There are no closed source languages. That's an urban legend. You can try to booby-trap a language, like MS tried to do to Java, but that won't work, either. You may recollect that MS failed in that effort, expensively(!).

      What you say is true...until someone like Sun patents a language feature that the language spec itself requires.

      What will you do then when you're trying to reimplement the language? Work around the patent? Please. Most patents these days are directly against the problem being solved, not against solutions to the problem, and when they are against solutions to the problem, it's usually when the solution presented is the only solution possible.

      This isn't like the good old days of Bell Labs, when software patents simply didn't exist.

      Stick your head in the sand all you want, but the problem of proprietary languages is only going to get worse as the patent situation itself gets worse, and the only approach to the problem that will survive is to implement everything using unencumbered languages, and the best way to guarantee that a language is unencumbered is for the reference implementation to be completely free (libre).

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    13. Re:Will this always happen. by AstroDrabb · · Score: 2, Insightful
      Some AC already made most of the points here, however I will parrot my opinion. As the AC said, the language means nothing today. It is all about the class libraries. Sun has not release all of their class libraries, why do you think RMS complained about all those import sun.* stuff? The same goes for MS and .Net. Sure, C# the language is a standard. But C# by itself is not very useful. There is no point in using C# over C or C++ if you leave out all of the .Net framework. That framework that MS made is _not_ part of the "standard" that MS made "open". There are no open docs on Windows.Forms or many other MS .Net framework class libraries. So basically if you are a normal developer that uses MS Visual Studio and C#, you will _not_ be writing applications with any cross-platform abilities. You will be writing an MS-Only application that relies on a proprietary MS .Net framework.

      I have heard from many MS guys that try to convince others that .Net is "open". It is not. MS made C# and the CLR open. While both of those are nice, they are not the important part of a program. Without the .Net framework class libraries being opened, MS keeps a lock on .Net/C# just as Sun keeps a lock on Java and the standard JRE/JDK.

      It's almost impossible to encumber open source software by using proprietary tools.
      Maybe for tools, but certainly not for proprietary frameworks. Frameworks are all that Java and .Net are about. They both try to present a _huge_ code library of pre-written, pre-debuged code to save developers time. However, if those frameworks lock a develoer into a proprietary framewrok, such as MS .Net and Sun Java, you are only left with a bare-bones language when it comes to Free/Open software.
      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    14. Re:Will this always happen. by linuxhansl · · Score: 2, Insightful
      If OSS it is about freedom, why do they make it difficult for us to choose a non free development method?

      Which is more free? 1) A society that allows you to vote for the end of elections, or 2) a society that protects you from doing so?
      The principle holds here. Freedom does not necessarily lie in maximizing the number choices.

    15. Re:Will this always happen. by slux · · Score: 4, Informative
      Uh huh, where to start... How this got modded up is beyond me. Clearly a troll.

      Stallman believes that if you like proprietary software then you're an idiot who does not deserve to use a computer.

      That's just slander. Do you have any comment implying something like this from RMS? I've never seen one.

      He also believes that all software should be "free" (but only per his definition of "free" - remember, to him BSD is not free, but to us BSD folks the GPL is not free, so it's a stalemate) and that all non-GPL software should be released under the GPL. He even goes so far as to clone some software and release it under the GPL, and to fork other open projects that he feels are not "free" enough (i.e., that don't use the GPL). Talk about a waste of effort! Don't add new features to a program, rather re-write it from scratch because you like the code but not the license.

      Bullshit. Try reading a bit on the FSF website. BSD is specifically identified as a free software license as are lots of others and they have a very clear definition of free software you can use to judge licenses for yourself.

      He may prefer the GPL because of copyleft but the GNU project itself chose X (which is MIT licensed) as their windowing system because it was free and ready.

      This article isn't about recreating something that isn't GPL either. It's about what happened with Motif and Qt all over again. And he wasn't even talking about a rewrite. KDE used Qt back when it was still non-free and that prompted the creation of GNOME.

      Using something like Java has real consequences. For *users*. People on *BSD, BeOS will have a hard time porting/running your software when there is no official JRE offered. Or you could happen to be running Linux on a somewhat less usual processor architechture.

      What has Stallman done that's original thought (the GPL doesn't count, I'm talking working code)? What hasn't he simply cloned for religious purposes? He didn't like the emacs license, so he cloned it
      *Sigh* Trolling real hard, aren't you?

      First of all, why would the GPL not count when it could be argued that it's one of the main reasons for free software's success and is used by something like 70% of free software?

      Second, EMACS is very well known to be the original work of RMS and he also wrote the original GNU C compiler. Many of the essential system utilities you use if you're using a GNU/Linux system are a result of the work of the GNU project. I won't even bother commenting on your idiotic remarks on GCJ.

      I must thank him, though, because his stupid insistance that every Linux distribution is "GNU/Linux" so turned me off that I started looking at the various BSDs as an alternative, and I found them so much better than Linux that I no longer have any Linux in my house, just *BSD and Windows.

      Your beloved BSD still uses some GNU components though. Such as the GNU Compiler Collection which includes "Stallman's Java-clone" and is used to compile each and every application you're using. And don't even get me started on the various GPLed parts. If you're using FreeBSD it also is pretty frustrating to install OpenOffice.org from ports because of the Java dependency. Fortunately Java compiles out of the box so you can still use it. On some other BSD that may not be the case and there are no guarantees that a newer version will still work. Time to go using Windows exclusively, maybe? After all, it has such a nice and free license and everything they do is completely original instead of cloning stuff and then releasing it under the restrictive GPL license.

    16. Re:Will this always happen. by sbrown123 · · Score: 2, Interesting

      It's only "well documented" in the sense that there's a nifty little tool that turns all public methods into pretty HTML pages.

      The documentation covers the public and protected methods that are available for use by programmers. Private methods, fields, etc. are not important when writing your own classpath since no one should access them anyways unless they are extending your implementation. GCJ contains many private methods within the classes that are not in Sun's JVM, and vice versa.

      If you tried to write a (non-trivial) program that used the non-trivial parts of the Java APIs (like Swing), using only the API documentation, it wouldn't work

      Its been done before. Heres an example: http://swingwt.sourceforge.net/

      I've written parts for GCJ by only using the API documentation supplied by Sun. I won't say it's an easy task. What the documentation says it's suppose to do and what the Sun JVM actually does requires some work on the implementors part. The only way around this is if Sun would allow JVM writers to view their source without worrying about the license concerns.

      There are many projects that do it this way. Look at Mono. Working from only a specification is quite common.

      OO.o issues, from my understanding, are because the free implementations of the JVM do not work as they should. With some tweaking, this is very correctable.

  2. The concessions by AKAImBatman · · Score: 4, Insightful

    only official Java APIs are allowed to be used

    This was already being done. There was a plugin interface that hooked into the AWT layer of the JVM, but that was something that was easily replacable by other VMs. Previous versions of OOo (probably from back when it was StarDivision property) used hidden APIs, but this was cleaned up in the 2.0 edition.

    Java JRE interested parties provide the support code and take care
    of QA, bugs etc.


    This sounds like they're moving the plugin code out of OpenOffice and into the JVM. Technically, this is where it belongs, but it's always nice to be able to support the largest number of VMs possible.

    OOo Java implementations must be encapsulated with well specified APIs

    This is just good engineering design. If you can't produce readable JavaDocs from it, it isn't a good API.

    OOo Java implementations must not check against Java versions or
    vendors, with the only exception of workarounding bugs


    Again, this is just common sense. Checking version numbers is a good way to nail yourself in the foot on future releases.

    OOo Java implementations must not use swing, either because no free
    swing implemetation is available or because it makes the user interface
    inconsistent, this rule might be relativated in respect to 4


    This is just common sense anyway. Using Swing would be detrimental to the GUI unless it was decided that the entire GUI framework would move at once. Such a decision would involve the entire OOo community.

    the Java baseline is 1.3.1

    This is the only concession I see being made. (1.4 & 1.5 have some *really* nice features.)

    The amusing part about this is that the whole tirade against Java in OOo is nothing but a farce. A quick check of the 2.0 code finds almost nothing that violates these "concessions", and they amount to nothing more than diplomacy anyway. (i.e. The art of saying "nice doggy" until you can find a big stick.)

    The truth is that Sun has bent over backwards for the OSS community, and all they get for their troubles are painful stabs in the back. Yeah, Sun's got some loud mouths working for them. But their actions have ALWAYS been honorable. Despite all the nonsense about "contamination", has anyone EVER had Sun sue them? I've certainly never heard of a case! And when Sun realized that the language was confusing, they updated future source releases with new language that EXPLICITY gives developers rights to whatever they remember. So no more excuses! If you want an OS Java platform, code it. Sun sure as hell isn't standing in your way.

    BTW, Mr. Stallman. How's Hurd coming along?

    1. Re:The concessions by GigsVT · · Score: 2, Interesting

      Your "common sense" is not too common when it comes to most Java apps I have ever attempted to use.

      There are two possible conclusions. Either all Java developers are idiots, too stupid to learn a real language, or these are important rules to nail down before they become problems. Since the former obviously isn't true, it must be the latter.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:The concessions by AKAImBatman · · Score: 2, Insightful

      Oh, so this must be the reason why building OO2 with a free java has been such a pita and required so much work...

      Such as? No one has come forward with any solid complaints against the 2.0 release. Almost all complaints (e.g. hidden APIs) are against the OLD version of OOo. If you have a solid argument then by all means, make it.

      however that really doesn't mean that one shouldn't be able to critizise SUN when they do something bad and stupid

      Except that they haven't managed to do anything stupid. They leveraged the Java platform with the full blessing of the OOo community to produce a quality product. That's smart. Rebuilding everything from scratch because you don't want to keep up with technological progress is stupid.

      "BTW, Mr. Stallman. How's Hurd coming along?"
      And has got exactly what to do with the story? Oh nothing, you simply thought you could score a cheap shot and start a flamewar.


      No, I couldn't resist that shot. Because Mr. Stallman has incited his own flamewar over absolutely nothing, while simultanously showing that his foundation is incapable of managing anything as complex as Java. Look at the Linux success and trace out which programmers are doing the most powerful work. You'll find that $$$ and hours are coming from IBM, Oracle, Sun, and other big names to make Linux useful. Same with OOo. It's not the GNU volunteers who are doing the bulk of the work.

    3. Re:The concessions by squiggleslash · · Score: 4, Insightful
      *shrug* The concern Stallman had was that OOo wouldn't be compatable with (real and hypothetical) Free Java implementations, a legitimate concern given the difficulty of restricting one's self to an "official" API. Sun themselves had the same problem when Microsoft came out with their own Java implementation, they were extremely concerned that people would create programs that would only run under Microsoft's JVM.

      They actually sued Microsoft over it. I don't know if you remember.

      You may feel that the good-practice inspired guidelines are stuff the OOo team would have done anyway, and that's well and good, but as nobody was sure that was actually what would have happened, it was worth the FSF talking to the OOo people to make sure.

      I await the news about Linus rewriting Linux in Sun's Java. Now, that'll be some flamewar, as you'll get all the "If an obscure proprietary method happens to be best for the job, Linus is absolutely right to use it and make the entire Linux kernel dependent on it!" apologists flaming those who do not consider wearing someone else's handcuffs "practical".

      --
      You are not alone. This is not normal. None of this is normal.
    4. Re:The concessions by Soko · · Score: 4, Insightful

      The truth is that Sun has bent over backwards for the OSS community, and all they get for their troubles are painful stabs in the back.

      *Sigh*

      This is not about whether Sun is a benevolent company or not, or if Java is a good solution or not.

      Is Java nice? Yup. Is it the right tool for the job? Obviously.

      Are most of the people at Sun trying to be a good OSS citizens? You betcha.

      Is Java Free Software? Nope. Not yet, it isn't.

      That's where all of the problems stem from.

      What if Sun suddenly did turn malevolent (Schwartz - one of the loud mouths - is no fan of the GPL, after all) could they do real damage? Yup.

      If a malevolent entity bought Sun - with a depressed Sun stock, it's a real possibility - could that entity do damage? Oh boy, you bet.

      It's not stabbing Sun in the back - it's protecting the backs of OSS developers and users now and in the future.

      Soko

      --
      "Depression is merely anger without enthusiasm." - Anonymous
    5. Re:The concessions by node+3 · · Score: 4, Insightful

      This is the only concession I see being made.

      Prior to this "agreement", all the rest of the terms you dismiss were not certain, the OOo team could have violated them for practical reasons at any time. Now that'll be much more unlikely. The FSF is being quite rational in criticizing the inclusion of Java code into the OOo project. The OOo team has agreed to not fall into the potential traps that the FSF fears. This is, on the whole, a very good thing.

      The amusing part about this is that the whole tirade against Java in OOo is nothing but a farce.

      In your clearly anti-FSF biased opinion, perhaps. You're not an idealist, but a pragmatist, OK, no big deal. But you'd have to be one hell of a cynic as well, to call it a "farce".

      The truth is that Sun has bent over backwards for the OSS community

      Prefacing the statement with "the truth is" doesn't make it true. What has Sun done that constitutes "bending over backwards"? In the OSS community, "bending over backwards" tends to mean making your code open source.

      Despite all the nonsense about "contamination", has anyone EVER had Sun sue them?

      Does the name "Microsoft" ring a bell?

      BTW, Mr. Stallman. How's Hurd coming along?

      What's that got to do with Java and OOo? Or is it just an ad hominem? I don't know who you are, but it's a good bet that Stallman has done more to make my life better than you ever will. A cheap shot won't change that, either.

    6. Re:The concessions by AKAImBatman · · Score: 2, Informative

      The concern Stallman had was that OOo wouldn't be compatable with (real and hypothetical) Free Java implementations, a legitimate concern given the difficulty of restricting one's self to an "official" API.

      Go program Java for a little while. The "hidden" APIs are not a necessary evil, or in any way desirable to use. The very design of the Java platform is so open that those APIs are almost impossible and completely unncessary to use. Pretty much all examples of this usage comes from the 1.1 days when a few APIs had yet to mature. Foolish developers went off and decompiled Java code to find "extra" features like they could in Microsoft software. Thus any occurances in OOo probably stem from StarDivision's work way back when.

    7. Re:The concessions by AKAImBatman · · Score: 2, Interesting

      It's the reliance on problematic (to the FSF) technology that this issue (flamewar? WTF?) is about.

      The FSF's failure to produce a JVM based on open specs is NOT everyone else's problem. If Mr. Stallman wants to fix the situation, he should be inciting his troops to fix their Open JVMs. Otherwise he can keep his trap shut, because he has no right to complain.

      emacs, gcc, gnu...

      Funny, it seems that EMacs and GCC have a lot of help from corporate entities. And what is "gnu"? I'm not familiar with that program.

    8. Re:The concessions by Anonymous Coward · · Score: 2, Insightful

      "Such as? No one has come forward with any solid complaints against the 2.0 release. Almost all complaints (e.g. hidden APIs) are against the OLD version of OOo. If you have a solid argument then by all means, make it."

      Just look at the efforts the RedHat devs had to put into making OO2 run with a free java and you will know what I'm talking about.

      "Except that they haven't managed to do anything stupid. They leveraged the Java platform with the full blessing of the OOo community to produce a quality product. That's smart. Rebuilding everything from scratch because you don't want to keep up with technological progress is stupid."
      Ah, the beauty of false arguments.
      1. You present a false dichotomy, as if the only option is to either use Java, or not keep up with technological progress. That's of course simply bs.
      2. Using a non-free platform (And Java is a non-free platform, at least until free implementations are truly ready) to build a free software application will inevitably produce problems.

      "No, I couldn't resist that shot. Because Mr. Stallman has incited his own flamewar over absolutely nothing, while simultanously showing that his foundation is incapable of managing anything as complex as Java."
      1. GNU's failure to deliver on hurd has nothing to do with the validity of Stallmans critic, nothing at all.
      2. That Stallman incited a flamewar over absolutely nothing is wrong for two reasons:
      a) He didn't even start this discussion.
      b) As already stated, using a technology that will inevitably pose a problem for the FOSS community is a problem, no matter how often you deny it.

      "You'll find that $$$ and hours are coming from IBM, Oracle, Sun, and other big names to make Linux useful. Same with OOo. It's not the GNU volunteers who are doing the bulk of the work."
      They may be now, after people like the GNU volunteers (ever thought about how useful a Linux system would be without the GNU tools?) made Linux a viable option.

    9. Re:The concessions by Richard_at_work · · Score: 2, Insightful

      *shrug* The concern Stallman had was that OOo wouldn't be compatable with (real and hypothetical) Free Java implementations, a legitimate concern given the difficulty of restricting one's self to an "official" API.

      I find it amusing that RMS is looking to ensure that a project will be compatable with 'Free' version of a language that was created, developed, fostered and made acceptable by a closed source company. Why isnt he promoting the use of a fully 'Free' language, like Python or similiar (no, Im not a python developer) and then he would have no worries about a controlling company damaging opensource projects in anyway.

    10. Re:The concessions by node+3 · · Score: 3, Informative

      Come off this nonsense people. Sun is not losing money hand over fist (they're more or less breaking even right now), and they've made it perfectly possible for others to replicate their technology. Why is the OSS community blaming their failure to do so on Sun?

      You keep turning this into an attack on Sun, and it's not. It's an attack on OOo's reliance on Java, which introduces compatibility problems with Free Software.

      In other words, you keep *completely* missing the point.

      Sun doesn't have to make Java Open Source, but that's not the issue at hand, is it? Relying on Java is not FSF-friendly, so the FSF will try to convince that project to "stay the course", as it were. There's nothing wrong or "nonsensical" about this at all.

    11. Re:The concessions by Soko · · Score: 2, Insightful

      Would you like to explain to me WHY THIS IS SUN'S PROBLEM? They have given everything away except for the actual rights to Java itself. If the GNU Foundation can't produce an Open JVM based on open specs and fully available source code, THAT IS THEIR PROBLEM.

      No reason to shout. The GNU Foundation not having a JVM isn't Suns problem at all. It is still a problem, however, and one that needed to be dealt with.

      If a malevolent entity hit Linus with a bus and acquired his Linux trademarks, and with the number of evil people out there it's a real possibility, could that entity do damange? Oh boy, you bet!

      This is non-sensical. As well, Linus' code is fully under the GPL - any one of the higher profile kernel devs can take over where he left off, and your "pie in the sky" Evil Doer would end up coding by himself. The same cannot be said for Java at present.

      Come off this nonsense people. Sun is not losing money hand over fist (they're more or less breaking even right now), and they've made it perfectly possible for others to replicate their technology. Why is the OSS community blaming their failure to do so on Sun?

      Sun is not losing money, but they are still a potential takeover target with their stock price where it is. Their tech is being replicated (which, if you RTFA, you'd see that this is the solution that everyone agrees is best) finally because the licensing restrictions were loosened quite a bit.

      Please listen - we do not hate Sun. We just will not blindly give up control of a major OSS project to someone or something whom we aren't absoloutely certin we can trust 5, 10 or 50 years from now.

      Soko

      --
      "Depression is merely anger without enthusiasm." - Anonymous
    12. Re:The concessions by Vellmont · · Score: 2, Interesting


      Would you like to explain to me WHY THIS IS SUN'S PROBLEM?

      I don't know if it's "sun's problem", but I would say it's a problem for sun. The problem is that no major linux distribution includes a JVM in its distribution. That makes the Java language far less usefull to developers. If you can't count on a JVM being on a machine, you then have to go through machinations to include a JVM in your software. Even that's difficult since Sun won't let you re-package the JVM.

      How is that Suns problem? Well it makes Java less usefull, and I assume Sun wants Java to be as popular as possible. Sun is still competing against Microsoft, and if Suns language is on Linux boxes, that's a win for Sun.

      They have given everything away except for the actual rights to Java itself.

      Actually one of the big sticking points is re-packaging Java. If they simply allowed that, it'd be included in at least redhat.


      If a malevolent entity hit Linus with a bus and acquired his Linux trademarks

      Huh? How does someone hitting Linus with a bus get them the Linux trademarks? Someone aquiring Sun is a real possibility. Mergers of large companies happen all the time. If you have to resort to ridiculous comparisons to make your point, you've already lost.

      and they've made it perfectly possible for others to replicate their technology. Why is the OSS community blaming their failure to do so on Sun?

      Now you're just making up arguments that no one has made. That's called a strawman argument and is a logical fallacy.

      --
      AccountKiller
    13. Re:The concessions by wangmaster · · Score: 2, Insightful

      Is Java Free Software? Nope. Not yet, it isn't.

      Would you like to explain to me WHY THIS IS SUN'S PROBLEM? They have given everything away except for the actual rights to Java itself. If the GNU Foundation can't produce an Open JVM based on open specs and fully available source code, THAT IS THEIR PROBLEM.


      There are a number of problems with your statements.
      1) To get Sun's source code, I believe you have to agree to the terms of Sun's community license, which has some severe limitations on how it can be used. This has serious impacts on the GNU foundation creating an Open JVM, for example, if you use their source to create your own JVM, you can only give out your executable to those who agree to the sun license and other third parties only for the purposes of evaluation.
      2) The Java Specification is very useful for helping to create a Java-like language. However, the implementation details make creating a full Java clone next to impossible with just the spec. There are also potential issues with Java implementations that dependent on third parties.
      3) You can't really use the Java trademark to refer to your own Open JVM. 4) Sun is trying to make it seem like they're very open source savvy, but what it boils down to is that they want as much control as Java as they can get. In many ways they are just as insidious as microsoft is. (FYI, I am a java developer and get paid to do Java. I like the language, and use it on it's technical merits, but the licensing sucks)

      If a malevolent entity bought Sun - with a depressed Sun stock, it's a real possibility - could that entity do damage? Oh boy, you bet.

      If a malevolent entity hit Linus with a bus and acquired his Linux trademarks, and with the number of evil people out there it's a real possibility, could that entity do damange? Oh boy, you bet!


      This analogy isn't even close to accurate. Someone could potentially perform a hostile takeover of Sun, or even offer Sun an amazingly crazy amount of money to be sold. That new entity could rewrite all the licensing they want going forward. Linus Torvalds getting hit by a bus would at worst kill Linus. Linux will still go on. It's possible that Linus' next of kin could do it, and take over the Linux trademarks, or hell, maybe they'd buy the Linux trademarks from Linus, but that wouldn't hurt Linux. Linux could be forced to be renamed, but realistically, that's not a problem. Linux is out there, given to the world, call it Linux, call it FoobarOS, it's the same either way. This is the beauty of the GPL model, and the Sun model doesn't come close.

    14. Re:The concessions by AKAImBatman · · Score: 2, Insightful

      Ok, I'm cooled down now.

      It's just not an "AKAImBatman" post without an insult at the end, is it?

      Sorry about that, but as you can tell I have a lot of pent up feelings about this issue. From day one all we Java developers have heard from the main OSS community is "Java is not free, Java is slow, Java sucks". This has been very much a last straw for me. I'm so pissed off, that I even took the lead on resolving the supposed "licensing issues" that are preventing Linux distributions from redistributing Java. With any luck, we'll see the one I'm working with including it soon. :-)

      The "corporate backers" clause is irrelevant. The FSF (it's not called "The GNU Foundation") is fully capable of managing highly complex projects (which was your original claim).

      Fair enough. The FSF has not proven its ability to manage these projects without corporate backing. Right now the FSF's concern is that Sun will disappear or tighten up restrictions. Look at it from the other side, though. Sun has invested a considerable amount in Java and has made it central to their business. Why should they take the risk that other corporate backing will dry up and they will be left to fund BOTH Java and the FSF?

      Stallman's position on Java doesn't rely on corporate backers, it depends solely on how Java meets his ideals.

      His position may not, but his ability to produce does. If he can't demonstrate that he is secure enough to be a custodian for Java, why should Sun trust him to be one? It's far better for everyone if Sun maintains control, but gives away all the info necessary to replicate their feat. I imagine that they're also getting pretty frustrated at the lack of a compliant GPL JVM. But since such a beast is not required by their business, they're not going to fund it.

      GNU is not just "'ls' and 'tar'". It's an *entire OS*, including libraries, a kernel, etc. It's a far *larger* project than Java.

      GNU is NOT an entire OS. There is the Linux kernel which is maintained by corporate backing. That is not in the FSF's posession. (At least, the last time I checked.) Then there is the X11 system. Also supported by corporate backing and also not in the FSF's posession. Then there is KDE and GNOME which are not in the FSF's posession. By the time you whittle it down, you find that "GNU" consists of a wide variety of command line tools, most of which are standalone and have nothing to do with each other. The few complex pieces (e.g. GCC) again are supported directly by corporations.

    15. Re:The concessions by fforw · · Score: 2, Informative
      But their actions have ALWAYS been honorable. Despite all the nonsense about "contamination", has anyone EVER had Sun sue them?
      Well.. it was not Sun, but ..

      From The History of the GPL:

      In the early years (1984 to 1988), the GNU Project did not have a single license to cover all its software. What led Stallman to the creation of this copyleft license was his experience with James Gosling, creator of NeWs and the Java programming language, and UniPress, over Emacs. While Stallman created the first Emacs in 1975, Gosling wrote the first C-based Emacs (Gosling Emacs) running on Unix in 1982. Gosling initally allowed free distribution of the Gosling Emacs source code, which Stallman used in early 1985 in the first version (15.34) of GNU Emacs. Gosling later sold rights to Gosling Emacs to UniPress, and Gosling Emacs became UniPress Emacs. UniPress threatened Stallman to stop distributing the Gosling source code, and Stallman was forced to comply.
      I think this case history makes the fears of the GNU people understandable if not justified.
      --
      while (!asleep()) sheep++
    16. Re:The concessions by shaitand · · Score: 2, Insightful

      "GNU is NOT an entire OS. There is the Linux kernel which is maintained by corporate backing. That is not in the FSF's posession. (At least, the last time I checked.) Then there is the X11 system. Also supported by corporate backing and also not in the FSF's posession. Then there is KDE and GNOME which are not in the FSF's posession. By the time you whittle it down, you find that "GNU" consists of a wide variety of command line tools, most of which are standalone and have nothing to do with each other. The few complex pieces (e.g. GCC) again are supported directly by corporations."

      Just to interject on a small point. The only thing you mentioned there that is part of the OS is the kernel. This annoys the hell out of me. An operating system is the software system that operates the hardware. An operating system provides the foundation on which you build a system usable by programmers or users, but it is NOT that entire system.

      The rest are libraries and applications living in userspace. The linux kernel has had contributions from corporations but was and is primarily developed by volunteers. If you recheck your list you'll find out that most of the corporate contributors are just volunteers who are now getting paychecks (like Alan Cox). Corporate interests have helped to speed development of recent releases of the kernel but the kernel existed before them and could exist without them.

      I would agree the FSF has not shown it could create a project as complex as java. However, the Free software community has developed solutions that are infinately more complex (like the Linux kernel). Actually even the first release of the kernel written by Linus alone was beyond the complexity of Java (although it hardly had the QA and stability of sun java).

    17. Re:The concessions by AKAImBatman · · Score: 2, Informative

      If you read my original post, you'd find that I have looked at the OOo source code and found no usage of "hidden" APIs. The closest thing that exists is a point where the JVM's AWT package is plugged into OOo. Plugin code exists for Sun and other JVMs. Any open source JVMs (e.g. GCJ) merely need to add their own plugin code. You'll note that JVM providers are just as responsible for web browser plugin code.

      I've said it before, and I'll say it again. Sun has removed all of the sun.* references from OpenOffice itself. If RedHat developers are having trouble compiling, it's because they don't understand how to plug their JVM in. I'm sure that this was resolved on the OOo mailing lists within an hour or two.

  3. Huh? by Anonymous Coward · · Score: 5, Funny

    "Points out his Newsforge about a something good..." Is this a quote from Zero Wing?

  4. Unbiased by zoloto · · Score: 4, Informative

    It is not an easy thing to write a balanced and informing article about this issue, but Bruce Byfield suceeded in this and we all owe him our thanks for that. I think that there is a great deal of good will on both sides of this discussion and we should *all* try as hard as we can to built upon this good will. By calling each other names we can only all end up loosing. We need not always fully agree with each other, but we should try to accommodate each other as much as possible and try to stress that which we have in common.

    This was also posted on the NF page.

  5. Re:JavaTrap? by AKAImBatman · · Score: 4, Informative

    Too bad they dont use something like TCL-TK or Ruby... but I kow why that is. There's a hell-uva lot of programs and libraries to use for free(as in gpl'ed).

    There's a hell of a lot more for Java. For example, there's no other platform that has as many high quality, cross platform database drivers. And for that matter, Java has quite a few free database engines (HSQL, McKoi, Derby (Cloudscape, etc.) At the end of the day, there simply isn't any other solution that's as well supported and ubiquitous as Java.

    At the risk of starting a flamewar, I have to say that I'm proud to have been a vocal early adopter that helped Java reach the status it has today. It's a good language, a good platform, hosted by a good company, and supported by many. Only the original Unix platform had such a profound effect on the industry.

  6. A surprisingly conciliatory attitude on both sides by Timesprout · · Score: 2, Insightful

    Well why not, after the damage is done and they have made themselves look very very stupid.

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
  7. Zealotry as a force for good by jmmcd · · Score: 3, Interesting
    The interesting thing here is that Richard Stallman's zealotry/passion (delete as appropriate) had the effect of improving something: "Stallman has learned that efforts to compile OpenOffice.org using the GNU Compiler for Java (GCJ) were close to success, and has amended the call to a request for help in continuing this work."

    As opposed to the type of zealotry which some people say is killing Debian.

  8. Conflict? Only one side was whining by ishmalius · · Score: 4, Insightful
    Can someone show me the complaints coming from the OpenOffice developers? I didn't see any. They seem to be doing all the work. They seem to be the ones with the conciliatory attitude. They seem to be making the changes in the interest of peace.

    What concessions did the "other side" make?

  9. Wanting to help out? by Anonymous Coward · · Score: 2, Informative
    Check http://developer.classpath.org/mediation/OpenOffic e2GCJ4

    Feedback wanted on how the different distributions are handling this, plus pacakge build instructions.

  10. double standards by Doc+Ruby · · Score: 3, Funny

    I'm shocked that Stallman allows GNU software to run on patented microprocessors and copyrighted, proprietary BIOS'es, without declaring jihad.

    --

    --
    make install -not war

    1. Re:double standards by kebes · · Score: 2, Interesting

      Your post may be intended as a joke, but Stallman is indeed pushing for free BIOS'es. He probably supports open designs for devices too. He certainly supports well-documented interfaces for all hardware. If you read Stallman's writings, it's clear that he identifies a difference between physical objects and ideas. Physical objects (including hardware) will always have costs associated with production, which is quite different from the comparatively effortless reproduction and distribution of software/ideas. His viewpoint is certainly extreme, but not inconsistent.

  11. The issues are good to air by syntap · · Score: 3, Insightful

    Many in the OSS community believe in soup-to-nuts software freedom, i.e. not only should the source to an app be open, but dependencies shouldn't exist on non-open software or libraries.

    The proposal to use GCJ was a good one, and I think raising these issues benefits open source even though it exposes the frictions between the players in the movement.

  12. It's not over until there's an open distro by Animats · · Score: 4, Interesting
    This controversy won't be over until there's an OpenOffice distribution avaialble that requires no proprietary code whatsoever.

    The reason this is so important is that if all the source is openly available, nobody can make it go away. It's essential to avoid "drug dealer marketing" - the first one is free, but then it's going to cost you. There have been too many products that started out "open", and then started to cost money once they had users locked in.

    The typical progression for psuedo-free software is

    • The product is free for download. A user community emerges.
    • A new version comes out, with modest restrictions and price, and the free version is deprecated.
    • The free version disappears.
    • The price goes up, and copy protection is added.
    • Market share declines.

    Examples are Intellicad, Sendmail, and QNX

    1. Re:It's not over until there's an open distro by Nailer · · Score: 2, Interesting

      Nice examples. You might want to add mp3, which owes it popularity to source code without a license attached uploaded to the ISO.

      Between about 1995 and 1998 a massive user community emerged. Then Fraunhofer Gesselschaft emerged after the silence and wanted $10,000 US per codec-using program (even the OSS ones).

  13. Nice that they decided to listen to their customer by nietsch · · Score: 2, Insightful
    Given some of the hostility to the larger community within OpenOffice.org, as well as Stallman's determination, deciding on the solutions and implementing them could still create problems. For now, though, at least the two sides are talking and trying to cooperate -- and free software advocates will get a version of OpenOffice.org they can install without pangs of conscience.


    Nice article, until he makes it sound like having priciples is a bad thing. The issue with FSF is not one of "conscience" but of licenses that can/will be an impedient of free use of the software. This goes beyond conscience and ventures into the realm of property rights that typically can deny others of free use. That is why Stallman in the past warned of the issue of using Sun Java.

    I think OOo need to look at FSF as representing customers that have a particular demand and accomodate that demand. All too often critics misuse the word "conscience" to disparage FSF community (customers) demands.

    This is simple "marketing 101" -- listen to the demands of your customers
    --
    This space is intentionally staring blankly at you
  14. Re:Get off your horse by node+3 · · Score: 2, Insightful

    However, I don't trust him as far as I can kick him. He had proved to me that he will always overreact to every situation, and suggest solutions that he is incapable of executing himself.

    You *can't* be serious! Stallman has been one of the most reliable people in the computer industry. You can *always* be sure which side of the argument he'll be on--even if it's not always your side.

    Personally, while I hold software freedom (in the FSF sense) as a value, I don't hold it as the ultimate value. In that sense, I don't find myself, in practice, always siding with Stallman, but it's absurd to say you can't trust him.

  15. Portable OpenOffice and Java by CritterNYC · · Score: 3, Interesting

    Personally, I was more than a bit disheartened when I first found out about how much of OOo 2.0 required Java. While Portable OpenOffice 1.1.4 worked quite well on machines without Sun's JRE installed, I was rather worried how Portable OpenOffice 2.0 would fare (just compiled a test alpha using the latest UPX beta, etc). If they split out a version that didn't require Java installed, I'd probably base Portable OpenOffice on that instead.

  16. Re:Free as in "do as we say" by Qzukk · · Score: 2, Insightful

    This "I have a right to YOUR source code" nonsense goes past what "free" really means.

    I suspect you don't understand what exactly is "free" in this situation.

    The GPL makes sure the code stays free. Remember "information wants to be free"? The FSF doesn't care about the programmers, as long as the code remains free.

    If you don't like it, don't use the GPL, don't contribute code to a GPL project, and for heaven's sake don't use the Linux kernel because you're too cheap to come up with an OS of your own or buy a ready-made one for your dvd player then whine when people bitch at you.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  17. Re:Free as in "do as we say" by mjh · · Score: 4, Insightful

    Ok. But BSD being "more" free is not really in dispute... at least I don't think it is. What's in dispute is whether or not BSD is a better licensing model than GPL. As someone who's published GPL licensed code, I don't really consider the BSD license that much. Mainly because it would irk me to no end if I bought a piece of software from someone else, and it turned out to have my code in it!

    BSD is great (IMHO) for things like reference implementations (e.g. for TCP/IP). For things that you want implemented everywhere. But if you don't want your code ending up proprietary then it's not as good. GPL is better at keeping your code open.

    Which is to say that there are advantages to each license, and it's not obvious to me that either is inherantly better than the other.

    $.02

    --
    Key to financial independence: Spend less than you earn. Save and invest the difference. Do it for a long time.
  18. Re:Free as in "do as we say" by killjoe · · Score: 2, Insightful

    Er um when you use BSD code aren't you saying "I have a right to YOUR source code"?

    --
    evil is as evil does
  19. Crap like this... by Anonymous Coward · · Score: 2, Funny

    ...is why I use AbiWord and Gnumeric.

  20. Doesn't the FSF seem a bit demanding? by Theovon · · Score: 4, Insightful

    It's interesting that OOo has become so influential that the FSF has decided to poke their noses into it. I for one think that making OOo's java code work with GCJ is a great idea and makes it easier on those of us who don't want to have to download Sun's VM. But I also find it a big disturbing that the FSF has the gall to make demands on projects they don't own.

  21. Re:Free as in "do as we say" by Vellmont · · Score: 2, Insightful


    This "I have a right to YOUR source code" nonsense goes past what "free" really means.

    I'm sorry, but I have a big problem with this attitude. Someone writes something and shares it with anyone who cares to use it. All they ask is that if you modify the software and distribute your new version that you share your source code changes. If you don't like it, don't take the deal. But complaining that a GPLed software author didn't give you everything you want is going a bit far.

    Arguing which license is "more free" is like arguing which ice cream chocolate or vanilla tastes better.

    --
    AccountKiller
  22. Awesome suggestion! by sneakers563 · · Score: 2, Funny
    I second the motion, along with an "Apple Fanboy", "Gentoo Fanboy" and "Debian Fanboy" choice. Really, why NOT a generic "Fanboy" entry?

    I'd also like to see any posts that use the phrases "just works", "just don't get it" or "the debian way" automatically modded -5; -10 if they are capitalized a la "The Debian Way". Posts that preface Linux with "GNU/" should be modded "Tiresome, Even to Friends".

  23. Exactly, this improves things for all by SuperKendall · · Score: 2, Insightful

    The best thing of all is if a really stable Free version of Java comes about, then there is no "Java Trap" anymore.

    That really was the most efficient solution, and Stallman being the eminent software developer realized this when he had all the facts.

    Really I feel it unfair to label Stallman a "zealot" when really it should be more like "informed and stubborn for the good of all".

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  24. Re:Free as in "do as we say" by Anonymous Coward · · Score: 3, Insightful

    more "free"?

    The question is "more free for whom".

    The BSD licences allow anyone to use the code for any purpose, but that can include taking a free software project proprietary. The GPL guarantees that a project cannot be taken and turned into something proprietary.

    RMS and the people who agree with him want to maximize the freedom of the end-user, even at the expense of the developer. The most extreme case of this is that RMS would like to require that all new software be released under GPL.[1] Very, very few people agree with this idea.

    Note that the GPL has some cool points. IBM was willing to license some patents to Linux for free, because Linux is GPLed. IBM can allow Linux to use its technology but can still charge money to anyone who wants to use this technology in proprietary applications. There is no chance that IBM will ever release any patented technology under a BSD license, since IBM would no longer be able to charge any royalties on that technology.

    Some coders hate the thought that their labour of love might be taken by someone else and turned proprietary. Those coders will prefer to release code under GPL. Other coders like the thought that anyone can do anything with their code, and they might even hate the thought of someone having to re-create similar code because of a licence incompatibility. Those coders will prefer a BSD-style license. Personally, I'm glad we all have this choice.

    [1] Google for the whole "Freedom Zero" debate. ESR made a public challenge to RMS: if you could pass a law requring all software to be released under the GPL, would you? RMS declined to answer. It's pretty clear he would, since he rejects the idea that "he who writes the code chooses the licence" (RMS wrote that this idea isn't "Freedom Zero", it is "Power Play Zero" because the coder is exerting power over the poor, poor users). Here, I googled and found it for you: Freedom or Power?

    ESR's challenge Freedom, Power, or Confusion?

  25. The glass is indeed half full. by hey! · · Score: 4, Insightful

    BTW, Mr. Stallman. How's Hurd coming along?

    Really, your post I thought was pretty good, but this last bit doesn't do the rest justice. Hurd doesn't have the mindshare to make the kind of rapid progress Linux does. What's that to you?

    The bottom line here is that Stallman has an agenda. A political agenda. A political agenda based on his philosophical principles. What's wrong with that? And, in this case, he was able to draw some attention to, and to advance the aims of his political agenda. Which is what people with political agendas do.

    Since, in the end, he didn't really do any harm to OO, and may even bring it some resources it needs (developers and testers), the final results are win-win, which is an uncommonly good outcome for a political dispute. Granted, a person with a more personable character might have got to the win-win scenario with considerably less heat and fuss, but unfortunately, my experience is that by in large the world effectively ignores those kinds of people unless they have the kind of credibility that only comes with having piles of money at their command. If things were different, then the world would probably be a better place.

    Even good people rarely place principle as high as convenience. Incidents like the recent Linuxworld editor ultimatum over Ms. O'Gara's nastiness are, unfortunately, a rarity. For most of the rest of us, principles are really just a vague, far away abstraction, whereas convenience and profit are very clear and immediate. Right and wrong would never play a role in any decision we make, if it weren't for the fear of exposure.

    So, we are stuck with gadflies, who vary widely in their admirability, but are universally unlikeable. Nobody enjoys being on the receiving end of a sting, which in every case is bound to seem overly harsh and unjustified. As unpleasant as they are to have around, gadflies play an important function. And if you don't like having them around, consider how fortunate you are not to be one. While I'm sure it has it's rewards, being driven against the current of the world must be a frustrating existence.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  26. Re:Conflict? Only one side was whining by Omnifarious · · Score: 3, Informative

    Not forking. Being willing to accept an OpenOffice version that had Java in it at all.

  27. The FSF and Stallman is correct by codepunk · · Score: 4, Interesting

    Lets just put a stop to the java zeolots right here and now...

    If you cannot package and distribute the application
    "with the JVM" it is not and never will be free.

    I happen to like java, but I sure would never use it in something I was gonna distribute.

    --


    Got Code?
  28. The copyleft JVM should have fixed its issues by Jamesday · · Score: 5, Insightful

    The FSF was being irrational. There was a JVM licensed with an FSF license which wasn't compatible with the latest Java standards. Instead of advocating fixing the broken code, Stallman was apparently advocating not using anything which didnt work with the broken code, to the point of forking a major project to avoid fixing that broken code. That's hardly an example of good programming ethics. Fix the bugs, don't complain about others not working around them.

  29. open source CPUs by Jecel+Assumpcao+Jr · · Score: 4, Interesting

    When are open-sourced based CPUs going to be available? Does anyone know of any available? I don't *feel* free with the current processor offerings available.

    Here you go. Check out the OpenRISC 1000 - I am guessing that it will be particularly interesting for you since the 1200 version has been used to demonstrate Linux. Of course the MIPS and Sparc clones can do so as well.

    Transmeta was the closest, since Linus worked for them way back when.

    Given that the native instruction set was top secret, I would say it was the least open source processor of all.

  30. Re:Conflict? Only one side was whining by CaymanIslandCarpedie · · Score: 3, Funny

    What concessions did the "other side" make?

    To stop bitching quite as loudly for a little while ;-)

    --
    "reality has a well-known liberal bias" - Steven Colbert
  31. Re:What about StarBasic? by DickBreath · · Score: 3, Informative
    Is StarBasic not powerful enough to use for creating wizzards and dialogs?

    StarBasic is powerful enough for wizards and dialogs. Many of OOo's AutoPilots are written in Basic.


    Is there more heavy lifting that really needs Java?

    Yes.

    Or Python, but...
    • PyUno bridge still has some problems
    • No python IDE within OOo, although you can (painfully) put python scripts into documents (starting in OOo 2.0).
    • The python that is internal to (i.e. "inside" of OOo 2.0) is still Python 2.3. (and is Python 2.2 in OOo 1.1.x)



    Or is this a matter of more people know how to code in Java vs. StarBasic?

    Using OOo's API with Java is much more difficult than using the same API from OOoBasic. It is the case that there simply are things that cannot be done in Basic...
    • write components
    • access OOo from an external program, i.e. a Servlet (Java) for instance to convert an uploaded excel file into OOo Calc, or vice versa.
    • not to mention issues with the lack of powerful features of Basic...
      • No data structures
      • No classes or user definable objects with user definable methods
      • No "collections" framework in Basic
    --

    I'll see your senator, and I'll raise you two judges.
  32. Hmm... still don't get it. by pavera · · Score: 3, Interesting

    I use the open office beta every day.
    I don't have java installed.

    All of the functionality that worked in 1.0+ works better in 2.0, and I don't use any of the additional features. Obviously, some people will want to use those features, but wow, aren't we always the ones yelling at MS for their stupid "wizards" and now we're mad cause we can't use the OOo ones? And isn't MS Access the bane of all db developers everywhere? And now we're upset cause we can't use our own half assed, not nearly as nice version of Access?

    Seriously people I don't understand. OOo 2.0 is not "crippled" without java, it works just fine for 100% of the existing (ie 1.0) functionality, and all you're missing is some gay wizards, and a half baked db frontend that crashes all the time. I installed java for about 10 minutes to check out the java features, and then uninstalled it, cause well they sucked. I know this is only a beta release and I'm sure 2.0 will be better.. but it won't be anywhere close to usable, not for anything remotely real.

  33. Only use organic fair-trade java by WillAffleckUW · · Score: 2, Funny

    it's the only way to go.

    in fact, you can't buy any in Fremont (in Seattle) if it isn't, and then you can open your office doors knowing you have good java.

    --
    -- Tigger warning: This post may contain tiggers! --
  34. Stop spreading FUD by JediTrainer · · Score: 2, Informative

    Seems to me that you can distribute the JVM without difficulty from Sun. To quote:

    The J2SE platform and the JRE are free to download and to use for commercial programming. They are also free to redistribute, if distributed with a value-add application or applet.

    Seems to me that OpenOffice.org qualifies for that.

    --

    You can accomplish anything you set your mind to. The impossible just takes a little longer.
    1. Re:Stop spreading FUD by synthespian · · Score: 3, Insightful

      (d) you do not distribute additional software intended
      to replace any
      component(s) of the Software,

      From:http://java.sun.com/j2se/1.5.0/j2sdk-1_5_0- ne tbean-4_0-cobundle-license.txt

      Seems to me this imparts Sun the right to stop any Linux or BSD distro from distributing any other non-Sun Java project.
      How does that sound to you? Restrictive?

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    2. Re:Stop spreading FUD by isilrion · · Score: 2, Informative
      Hmm... Seems to me that
      11. Export Regulations.
      All Software, documents, technical data, and any other materials delivered under this Agreement are subject to U.S. export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with these laws and regulations and acknowledge that you have the responsibility to obtain any licenses to export, re-export, or import as may be required after delivery to you.

      is restrictive enough to make it illegal for me to use it (or for anyone, regardless of his country, to distribute it to me in any way without violating Sun's agreement). If you belive that's free...
  35. Re:no more "Java Trap" BS? by QuantumG · · Score: 2, Insightful

    Blah, if OpenOffice were to actually use GCJ there would have been no argument in the first place. The problem is they want to use third party code that has been written for Sun Java not GCJ. It's surprising, it really is. When people write stuff for Mono they don't go looking for code that someone has written for .Net and expect it to work out of the box. But when people write stuff for GCJ they always expect stuff written for Sun Java to work out of the box.

    --
    How we know is more important than what we know.
  36. this was no "accident" by cahiha · · Score: 2, Interesting

    Sun seems to have a clear strategy of trying to incorporate their proprietary version of Java into open source projects: Mozilla, OpenOffice, Gnome, Apache, etc. But a piece of software ceases to be free when it depends in an essential way on proprietary software.

    Fortunately, open source developers are noticing this more and more and are starting to take countermeasures. Hopefully, in the long term, this will lead to unencumbered versions of Java becoming available and acceptable.

    1. Re:this was no "accident" by kaffiene · · Score: 2, Insightful

      Anyone can produce a JVM. There are several good FOSS ones out there now, as well as AOT compilers with GCJ nearly fully complete. There are NO legal impediments to ANYONE producing their own JVM and there is NO Sun-only bits in OOo.

      Quit spreading FUD.

  37. Java Trap Illusion by virtigex · · Score: 3, Insightful

    This whole issue seems totally unnecessary. Stallman's "Java Trap" is only relevant because FOSS implementations such as GCJ do not implement the full Java 5 standard. The solution to this would be update or make a FOSS version of Java that implements Java 5. It's not a trap if there is an obvious way out. If you don't want to go the obvious way out (because it takes too much effort), then the only thing that is trapping you is your attitude.
    Also The Harmony project (if it is successful) would seem to lay to rest any FOSS advocate's qualms about Java.

  38. Re:KDE QT dependency by conteXXt · · Score: 2, Informative

    You are kidding I assume?

    TrollTech re-licenced QT to something GPL compatible under duress.

    Here's hoping the same for Java.

    --
    The truth about Led Zep should never be told on /. (Karma suicide ensues)
  39. IHBT by flimflam · · Score: 2, Informative
    Ignoring the fact that IHBT, I couldn't help but respond to this:

    He didn't like the emacs license, so he cloned it.


    Of course you know that he wrote emacs (it's not a clone of anything). Oh, and gcc.

    --
    -- It only takes 20 minutes for a liberal to become a conservative thanks to our new outpatient surgical procedure!
  40. Re:What about StarBasic? by thisisauniqueid · · Score: 2, Insightful

    You *do* want OOo 2.0 -- it is dramatically better than 1.x in many, many ways that don't require java. I recommend trying the packages in the "fedora development" RPMs (what will become FC4). They are very usable today. Some things you'll notice immediately are dramatically improved startup time, better file format support, overall higher polish, filled-in feature gaps. The pieces you'll miss by not having Java are covered in other posts. Briefly: wizards, and the new database frontend (Access clone). You probably don't need them.

  41. FSF programmers... by Per+Abrahamsen · · Score: 2, Insightful

    There are close to none these days. FSF is mainly a legal and political organization. Programming on GNU projects is done by volunteers, or contributed by other organizations.

    Of course, you can be a volunteer programmer for FSF working on OO.o, but that is hardly different from being a volunteer programmer working on OO.o.

    What you can do is to be a volunteer on OO.o and be aware of the need of the GNU project ( acompletely free system). Which I suspect is what RMS hoped for in the first place.