Java Fallout: OO.o 2.0 and the FOSS Community
Joe Barr writes "Bruce Byfield has an interesting look at the 'fallout' between OpenOffice.org and the free/open source software communities because of their reliance on Java in the latest release. As he says, "It seems a decision based largely on practical considerations -- and with a disregard for the consequences for both the rest of the free and open source software (FOSS) communities and the future of OpenOffice.org itself." This is an issue that is not going away."
Who cares if it's using a non-Free java or a non-Free toilet paper? As long as it DOES THE JOB, it's good enough for me.
The only virus I've ever had infect my Windows computer was Java based, installed due to a flaw in 1.4.2 and some website I visited I suppose. I don't feel any better about Java being integrated in some way that I don't understand with Open Office, than I do with Word using Macro files, or offering VBS integration perhaps.
Saskboy's blog is good. 9 out of 10 dentists agree.
Just re-write everything in Visual Basic. That should make FOSS advocates happy.
I'm a big tall mofo.
is there lack of a command line interface that I can script with bash
Lots of people say that this doesn't matter; as long as OO.o works well, who cares about what free or un-free components it uses. The article does an excellent job outlining the real issues here.
Although it's true that functionality is important, at what cost? Using java not only adds dependencies, but dependencies that some parties are uncomfortable with. Corporate adoption may be slowed, as OO.o isn't a completely "free, fully functional" product anymore. Some of the core features (wizards) require java. Even though a wizard isn't "core" functionality, they're something that people in a workplace would likely need to use.
Either way, this is a good article... it explains the issues in a very clear way.
I store my recipes online (the way nature intended)
A few years back MS made a lot of fuss about Java while developing an alternative (.NET). In the process, they've planted some seeds such as "Java is neither open nor free!", and "Java is lock-in!", or the confusion surrounding Java on Windows, thanks to the MS VM supporting only v1.3.
.NET-based or native code. So if you, the open source community, cause more fuss over Java and whine about using it, then Microsoft has truely succeeded in it's FUD plan over Java.
I'll tell you all now, I'm a Winodws developer and I write C# code. For us Windows devs, no one uses Java anymore; if you do, it's for support of an existing product. Virtually all new projects are
Tech, life, family, faith: Give me a visit
John Carmack rips Java a new one here.
If someone says he and his monkey have nothing to hide, they almost certainly do.
Free as in not free enough? Give me a break
Can't these features be ported/compiled with gcj and run as native binaries?
Paying taxes to buy civilization is like paying a hooker to buy love.
1) It's not write once/ run anyware.
... and worse, there's
2) It's slow.
3) It's not on every machine.
4) It's dead as a web applet, replaced by DHTML and forms.
5) It's a pig.
6) It's not open source.
A noble effort, kudos for Sun for trying;
but it's just not cool
just no real advanntage to using it.
I wonder if this will lead to more effort being spent on free JVM clones.
Or even diverting effort from mono.
Could Sun have planned it that way?
Is Betteridge's Law of Headlines Correct?
Kinda ironic that Novell's Mono (with root in Microsoft research) is the most promising free VM these days. Too bad Parrot doesn't seem to have java running on it...
"A small but vocal minority.."
Apparently nobody has cared to complain to the marketing people. Not that I want them to, lol.
Java is free, people. Java is probably already on most desktop computers. Sun gave us OOo, and still do 75% of the programming. Unless you're willing to reprogram the Base, HyperSQL, and the other components that require java in C++, then don't complain.
You're getting an office suite, which, while it admittedly isn't perfect, it's definately the best *value* out there.
Jay | http://oldos.org
I read this earlier. If they're going to use java, they should at least make sure it works with GJC out of the box. The one Java alsmost all distros ship with.. So redhat et all. don't have to jump through hoops to get it installed.
I sometimes wish Linux had a application packaging system like MacOSX where you have the option of brining tons of libraries with you hidden under a file system pretending to be an app icon. It just works (most of the time). I'm tired of ldd.
I think that this is being blown out of proportion. The integration of java into the latest version of open office, although a little annoying, is not something that is going to keep me from using it on a day to day basis. Especially considering that all of my computers have java installed anyway.
I love to deploy my packages
There were some early security flaws, that are now fixed. OK. It is bloatware. Fine, it's slow. Alright, it's a PITA to work with on other projects. Seriously, what's the problem with Java?
Huge files and long load time should turn you off. Java does, in fact, allow for faster development. It also allows for even greater cross-compatability.
So tell me, what's wrong with Java?
Silence is golden... and duct tape is silver.
If they rely on coffee to stay awake to the wee hours hammering out code, hell, I say let 'em drink all they want! Whatever gets the code out, man! Matter of fact, I'm going to have me a big cup o' java right... ...uh, nevermind.
I think the article makes some interesting points, such as:
Some might argue against Schönheit's characterization of C++ as complex or Java as being not slow. However, technical arguments are in many ways beside the point.
What I got out of it is that the Java environment makes it far easier to add features to the current OO. From the article:
Java allows more rapid development of components for OpenOffice.org, without struggling with the complexity of OpenOffice.org's C++ build environment. People complain about releases not being quick enough and when Java is used to make the build environment less complicated, people bitch about it not being open source. You can't have your cake and eat it too.
And let's not get started on IDEs...
I'm not a big fan of Java. I feel like cross-platform programs can be written in a better language and can intergrate into the user's native GUI. The only company that can pull of using Java in Sun. Hell, they've put Java everywhere in Solaris.
Free, Open Source .NET implementation
Free, Open Source Java - oh, wait, there isn't any. No, really, there isn't. Read 1.3, 1.4, and 1.5.
Whether or not the complaints are sensible, I've got to think that if this "fallout" involved more than a tiny handful of disgruntled people I would have heard about it before this.
What I'm listening to now on Pandora...
and would have been found in as much time as it took you to post.
I don't want knowledge. I want certainty. - Law, David Bowie
I cant see this making that much of a difference. Is there going to be a price tag on OOo? Will it actually affect any end-users. I doubt it. The only people this will affect are serious afficondos of the GPL. They are just cutting off their nose to spite their face. OOo is a great suite. I havent tried this new java dependant version, but I cant see any actual practical implications. Oh noes, java is owned by sun!11!!!one!!1! So?
I hear that you can only run the software on non-open hardware platforms! It should require a GPLed CRT and CPU to run!
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
What would be nice is a ppt reader to go along with them...maybe Evince could be made to read ppt?
As for Java, I am only interested in the subset being promoted by RedHat - the free gcj/classpath variant. Call it FreeJava or whatever, but to me anything else is unacceptable. Come on folks, we came this far insisting on free software, don't give up now over one lousy VM and language spec.
Interesting way to try to make sure Java gets installed on lots of PCs. We're in the middle of a marketing war it seems. What is it about Java ? MS desperately don't want it installed to the point of creating a clone and Sun are desperate to get it installed.
Anyway. If you have objections to OO, what are the alternatives?
KDE: Koffice
Gnome: Gnome Office
Windows: ??????????
Government of the people, by corporate executives, for corporate profits.
From TFA,
"By contrast, Red Hat and Fedora prefer to build OpenOffice.org with the GNU Compiler for Java (GCJ), which is not only a compiler, but also a free JRE. This was Red Hat's strategy with earlier versions of OpenOffice.org, and Red Hat engineers are attempting to continue it. Caolan Macnamara, a programmer at Red Hat, has reported limited success compiling earlier developer builds of version 2.0. However, GCJ is not yet a complete replacement for official releases of Java, and adding patches makes the strategy painstaking and laborious at best."
- vimal
Since a long time there is nothing that prevent you to bring you own OSS JVM !!! This also include looking at the RI (the Sun BM) code and passing the TCK (the stuff that let you put the "compatible" logo and use the brant) for free as long as you are an organisation.
/. FUD about Java is IMHO nonsense, if somebody do not like Sun version, you can go and implement it your own way without any limit but your creativity !!!
;-)
So all the
This is fact, so plz stop the Java bashing.
Personally, I think Java has helped and is still helping Linux to enter the enterprise market by bringing to competitive solution. And no other solution is doing this better than Java !
So, event if this is not the saint graal, this is one of the best weapon we have to fight the empire
Has the open source community been reduced to a large group of lazy, whining bastards? If you don't like the way it is written, fix it your damn self instead of wasting your efforts bitching about it. If as much code was written about the topic as complaints, the issue would have been resolved already.
Anyone with any further complaints, climb the stairs out of your basement and tell your mother.
Karma Clown
I haven't heard anything so retarded since the last time I heard steve balmer give a speech. How excactly is ".net much more free than java"? Last time I checked, microsoft was not giving away any open sourced versions of any .net compilers without at least purchasing the operating system, so it's not really giving it away, plus its not open sourced. On the other hand, you can freely download jre and jdk from the sun website
and though I'm not sure whether that is open sourced or not, there is always the open sourced blackdown java implementation.
So the closest thing I see to irony here is that in order to defend microsoft, you have to be totally ignorant to the everything, much like all of microsofts products.
OpenOffice.org is released as an open-source license, right? So if they have such a big beef with the direction it's going, then someone can create a fork of the project and put the work into ridding it of this supposedly undesireable Java dependency. Or pick up the codebase, write all the currently java-dependent code in C++ and submit it as a patch.
To me, this sounds like a bunch of politicians and lobby activists trying to make the most noise so that they achieve their respective ideological agendas. As an end-user of OO.o, I really don't care either way as long as the functionality is there. And, afaik, the current Java license allows for redistribution of the Java Runtime Environment so they can't retroactively pull that license and prevent people from doing something they've already granted.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
Alright, assholes... who's going to rewrite the only major competitor to Microsoft Office because of some possible philosophical nonsense?
It's still open source, right? So fork it and rewrite it as an ncurses emac extension. I'm sure Joe User is really going to fall in love with that one. "Hey guys! We can type up our spreadsheets and text documents and save them in an MS Office compatible format, or learn emacs, lpr, and not work with anyone else because we're not sure if Java is going to be compatible with our philosophical ideals in the future."
You'd think someone around here had heard about the law of diminshing returns. I guess that's refuted with one word: Gentoo.
Faster development than what?
Java has some benefits. We use it for a lot of projects (in preference to C, C++, VB) where I work. But never where development speed is a priority.
Okay, maybe in applications with complex thread interactions, but you don't write those at all if you can easily avoid it.
In fact I can't think of a popular language that is slower to develop in. Our experience with Java has been pretty negative in that respect.
Fork it
KNEEL BEFORE ZOD!!
Here's a case where the FOSS (Free/Open Source Software) acronym doesn't work, because Free Software and Open Source Software are not the same thing.
Practical, pragmatic decisions like using Java are not a problem for Open Source. That's what Open Source is: developing software in an open manner because of a belief that software developed this way is technologically better than closed-source software. It does not insist that every tool (or language) used in the development process be Free Software or Open Source. From a practical standpoint, it is sufficient that the tool or language meets the needs of the developers and is available on the required platforms, and does not appear to be a patent or other legal liability.
Free software on the other hand, insists for idealogical reasons that any software or tool which is not completely free is deterimental to the community. It's important to have respect for this opinion, but it is not a catastrophe for the OO.org team to choose the Open Source route.
Hmm, sorry I think I misinterpreted your statement, but am too lazy to research the context of what you were saying...
You can freely download .NET compilers from MSDN, and there is the open-source Mono. I don't see the difference.
-mkb
Pardon my hazy understanding of the subtle issues surrounding Java and .NET, but isn't the major problem not so much about the JVM or the CLR, but all the libraries that applications written in either C# (Windows forms) or Java (com.sun.whatever) tend to use?
Well, that , and that either "standard" is subject to change without notice due either to paranoid-possesiveness "No we won't define an ISO" (Sun) or to gorilla-sized "We are the standard despite the stinkin' standards bodies" (MS).
"Provided by the management for your protection."
Fork it.
KNEEL BEFORE ZOD!!
Silly open source developers - putting practicality and pragmatism above more important things like dyed-in-the-wool political viewpoints. Next you'll be telling me they're all off using these newbie Linux systems, rather than diligently waiting for HURD to stabilise like they're supposed to. Tch.
. C has shortcomings
. C++ has more shortcommings than C
. Java replaced the C/C++ issues with other issues
. C# / Mono replaces Java issues with newer issues
Sun, IBM, HP, MS should know by now that they can create a modern ANSI/ISO standard based language including standard libraries way beyond stl/iostream that makes solution building easier?
Yes, it would have to be a patent free language with patent free libraries.
Why use java anyway?
Java is complete shit.
I despise Java and javascript with a passion.
If you want to drop a machine to it's knees, run some java..
Get rid of it..
Also, did OO take care of the printing problems?
They had made access to kprinter an absolute pain in the ass, I ended up going DOWN to OO 1.1 because of piss poor printing capabilities.
I have a myriad of network printers all of them serve different purposes and the more recent versions of OO (whatever shipped with Suse 9.2) wouldn't let me use kprinter without major pains.
I said to hell with it and loaded 1.1
Overall OO is a decent product but it needs some things seen to and they need to dump that damn java. I wish everyone would dump java..
According to TFA, OpenOffice.org requires Java for some accessibility features to work. If that is in fact the case, I can't help but wonder why Ubuntu includes it in the default installation as doing so seems to contradict their philosophy regarding using only free software that is accessible to everyone.
For those of us who still believe His message of compassion and peace is important, I ask you:
How's the anger management going?
Now I hate Java just as much as the next guy, (well probably moreso, but anyhow...) but I've compiled and used OpenOffice 1.x many times, and let me tell you--Java is not the problem. OpenOffice is *already* enormous and bloated and slow. It also already requires Java just to build the darn thing, or at least it did when I built it. Whether it depends more or less on Java, I don't care as long as it gets at least two of smaller, less bloated, faster...
:)
So, ok, now that we're agreed that we aren't necessarily talking about a technical issue here. Again, what's the problem. That "Java isn't open source"? Well why don't you ask IBM to open up a JVM for you. Or, better yet, write your own! Java is widely used, readily available, and actually pretty darn open as these things go.
So what's the problem. Ideology? Zealotry? Arcane license disputes? Well, it's nothing that'll get in the way of me and my word processor. Just wake me up if it gets larger, more bloated, slower...
pb Reply or e-mail; don't vaguely moderate.
The .NET SDK (compilers and everything else you need) is free from MSFT.
For everything else, there's Mono and dotGNU, and plently of fledgeling C# compilers.
Blackdown isn't open source:
We each are dedicated to the professional development of the Java platform for Linux based on the community source concept. We see participation in the Blackdown project as a cutting-edge opportunity for intellectual cooperation between the open source community and the commercial software industry. We each are committed to abiding by the agreements we've made with Sun and other technology vendors. We aim to use their good will to further the cause of independence for software developers around the world. A bridge between the open source community and the commercial software development world is to everyone's advantage, and we would like to exemplify that relationship. We believe that the vendors with whom we partner are committed to the same ideals.
It's a free-for-non-commercial-use linux port of Java. It's stillborn in the corporate world.
I don't need no instructions to know how to rock!!!!
It's called python.
People are just being crybabies. All of the functionality that relies on java is new, and in my opinion non-core. Yes, they need to clean up the menu system so that choices that require java are greyed out if its not available, but 2.0 is worth it just for the ui enhancements and better filters.
Base is a lame Access knockoff that crashes all the time. It won't be stable until OOo 3. And why do we care if we can't use wizards, aren't we always lampooning MS for their endless "wizard to create xyz"?
What now we're mad cause someone used the best language available (to them) to produce some new features? I though FOSS was about choice, but I guess thats only if you pick the language that FOSS condones... You can pick anything as long as its lisp and emacs! Anyway, I'm not a java fanboy, I much prefer python or perl, but java does have its place and there are alot of coders who know it, so now we're saying you can't develop OSS in java.. that's a great stance to take.
Grow up, download the JRE, or don't whatever, I've been running the 2.0 beta since it was released without the JRE and I haven't missed anything, for what I need an office suite for it works great. To be true I did install the JRE to check out Base, but it sucks, and I ditched it after about 10 minutes.
I'm not going to claim that it's my favourite language, nor am I going to pretend that I prefer it to something that's fully free/open source, but it serves its purpose. I'm a computer science student stuck somewhere between first and second year (I switched faculties, so I'm behind), so I've been learning both C and Java concurrently. Because the learning language is Java, I have more experience in that, but I find C more fun. However, I am not going to hop on the OMG! JAVA IS TEH SUCK!!11! bandwagon because it does have some merits. Some were mentioned by the article, but in my personal experience, the main thing that I like about it is its portability. If I'm looking to download a program that doesn't have to run fast, and I want to use it on both my Linux laptop and Windows desktop, I'll look for something written in Java so I don't have to worry about either Mandrake or Windows flatly refusing to run it. The extra (and basically one-time) step of downloading the latest version of Java onto my computer before I can run a Java app really doesn't compare to desperately Googling around for something that will definitely not screw up due to OS issues when I try to install it.
Ok, now... back to the article before I get too far off-topic. If Open Office works with Java bits in it, that's great. I don't use it much anyway, since emacs, vim, or even vi will normally serve my purpose.
"Although it's true that functionality is important, at what cost?" .net are Java shops. This non issue will not slow down deployment one bit.
Simple. Every and all costs. I program that is not "functional" is useless.
" Corporate adoption may be slowed, as OO.o isn't a completely "free, fully functional" product anymore."
I guess you are right here. I mean so many companies worry about using Java. I mean it is not like java is "free as in beer". Guess what? A huge number of corporations already use Java for internal development. Those that are not tied to VB or
This is yet another religion war that really means next to nothing. It is right up there with the GNU/Linux fight and BSD vs GPL.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
Okay after reading TFA, I think there is good reason for concern. I can also see the possibility of additional compiling projects. It's my understanding that since these are Java programs and there are programs that compile Java into binary. So I'm thinking we'll see custom OO.o distros featuring "now without Java dependancies!"
And why not? That's the primary strength of the Open Source movement -- don't like where a project is going? Fork or customize in some way. Ultimately the popularity of the standard package versus the customizations will steer the project in the most popular direction.... in theory. (There are some hard-headed asses out there who, as in the case of XFree86) won't bend to popular demand and a completel fork would result. But the bottom line? The public should have its way if it wants it bad enough.
Sun has a stake in the acceptance and popularity of Java. The motivation behind this should be fairly obvious. It's my understanding that in the future, Java itself will be open sourced and will ultimately take away a lot of the argument that many FOSS people have against this situation. (The other part, asside from the license stuff, is the poor performance... I hate Java performance sometimes...sometimes it really seems to drag.)
You are joking Right?
Esclipse
Help fight continental drift.
Just because Sun java isn't free doesn't mean there aren't alternatives out there.
.NET has Mono and DotGNU. That's two. So how is it "much more free"?
Kaffe,
GCJ,
Jikes RVM,
Cacao,
and
others.
Or emacs using lisp
thank God the internet isn't a human right.
My first grammer nazi reply! I must finally be making it big on /. -- I think I'm going to frame this post.
:-p
Jay | http://oldos.org
i wonder if this is what happens when projects believe themselves too critical to ditch. similar bad sentiment caused a massive swing away from XFree86, i see no reason why it couldn't happen to OpenOffice. this is an issue they need to get on top of *rapidly* before any serious moves begin in this direction... :-\
Hell, I thought someone had ported Fallout to Java. :(
#19845
Given that it's perfectly legal to implement a system like Kaffe, given that it exists, that it can be done if you absolutely must, what is the actual issue with using Java in Open Source projects? Lord knows there are _tons_ of FOSS projects written in Java out there...
If the issue is just the Sun license and the "non-official" status of projects like Kaffe, to that I just have to say, guys, get over yourself. If you don't like the Open Office folks writing functionality that depends on Java, write it in C or whatever your self and contribute it. Seriously.
As far as end users? They don't care what something is written in. They want something that works. To that end, placing yet another installation requirement in the chain isn't great, but at the same time, the vast majority of user installations ( including on Linux ) simply aren't complete without a working JVM anyway, so... what's the big deal again?
"It seems a decision based largely on practical considerations -- and with a disregard for the consequences for both the rest of the free and open source software (FOSS) communities and the future of OpenOffice.org itself."
so, 'practical' is a low priority for open source? bah... damn nurds!
I see so many comments calling out moderators who make questionable decisions, and the moderators, without fail, NEVER RESPOND!!! Well I'm here to change that! For at least this one.
Yeah I'm an idiot, who couldn't read the Fucking Article. And I modded the grandparent insightful because of the aforementioned idiocy. I'd like to promise that this won't happen again, but who am I kidding?
On behalf of my fellow idiot moderators who committed this atrocity, I apologize for being retarded.
thank you for trying to teach me
I understand being burned by a specific application will make you averse to using that application in the future, but I wouldn't shy away from Java as a component of some larger application simply because it caused a problem for you personally once.
The free and open source software community is responsible for making sure bad implementations of important tools are fixed quickly and effectively, and I don't think it's the technical arguments against the use of Java that are the crux of this debate. It's the idea of slowly creating more and more features within OpenOffice that rely on a critical component that is itself not free.
http://jeffkrimmel.com
They should have used .NET, ironically, since it's much more free than Java is.
.NET is 100% proprietary outside of the meaningless ECMA standards. Is this some sort of troll that completely tricked the moderators?
No freakin' way.
For what it's worth, Sun will be the largest contributor of OSS code in the world this Summer, if they aren't already.
-- Microsoft is the most expensive commodity operating system and office suite vendor in the marketplace.
MOD PARENT UP, because corporate types reading this deserve to see the answer.
Are there any legit reasons that they didn't use an OSS alternative, like Python? It seems to satisfy all of the issues mentioned in the article...am I missing something?
BenCurry.net
ummmm two things wrong there... A. .NET IS Java (1.3) Numerous lawsuits were filed, some lost, some won, but ultimately, Microsoft is still producing .NET
Secondly the very site you link to has links to 15 FOSS JVMs Some of which attempt to ensure full Java 2.0 suport.. (read JRE 1.5)
So what's the issue here? FOSS has a harder time keeping up with Sun's Java development, but because mono was ripped off by a fleet of laywers, FOSS developers can more perfectly implement it?
Oh yeah the problem here is someone is actually using Sun's Java in an Open Source app, which means it isn't FOSS... FOSS is an ideal, and you can build entire distro's off of it, but it's not going to appeal to everyone. I have Sun Java Installed on Debian Oh nooo... IMO your efforts are wasted trying to make the _entire_ open source community embrace FOSS principals. It's a lost cause, because free as in beer will always be embraced by part of the community.
https://www.gnu.org/philosophy/free-sw.html
Java is many things. It is a programming language. It is also a runtime environment in the form of a protable virtual machine. It also comes with a huge class library.
For some reason, that monkey Miguel went and decided to write his own version of M$'s Java clone, C#/.NET, for "Linux" (i.e. Unix-like OSes) to undermine everyone else's work.
Now, you can get branded Java from people other than Sun e.g. IBM. IBM is currently a great favourite of the slashdot peanut gallery.
In addition, gcc comes with a Java-language to native code compiler as well as byte code (to run on the evil, nasty closed-soure Sun (or IBM or whoever's) JVM).
If you don't like Sun, or IBM, or Blackdown or kaffe's JVM, including their JIT compilers which can optimise to exceed the efficiency of statically-compiled code, then you can always revert to gcc's Java language compiler.
However, I'm sure these facts will be conventiently ignored for the sake of a good, heated argument, and many rants.
Stick Men
"I despise Java and javascript with a passion."
Since you don't realize the two are not even related i would say you are not qualified to comment. So, turn off daddies computer and go back to your after school special.
...isn't it? Remember how KDE was slammed for their non-free license and what that led to?
No, Stallman won't be happy with OOo - not at all, but at least the vast majority of OSS users will get something out of it.
BTW, OOo 2.0 rocks - just thought I should share.
"...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."
What a lot of people in the FOSS communities don't realize is that the majority of users just care about "free as in beer", which fits Java and OO.o.
If the FOSS developers don't like it, they can go ahead and fork. It would be interesting to see how far an OOo fork gets without Sun backing. Maybe now RedHat can finally put real resources behind a project and not just the odd developer or two behind firefox and X.
Read my post if you want to have a feel for how difficult it is to install Sun's JDK on FreeBSD. There are so many twists and turns here that when I reinstalled FreeBSD, I decided to install Kaffe instead to learn Java with (needed for future classes; language use not under my control).
This may be flamebait, but one of the main reasons why I haven't used OpenOffice on my computer is due to these Java dependencies. OpenOffice not only requires Java, but it specifically requires the Sun JDK. Some users may be asking me, "What's the problem?" The problem with that is that there is no binaries for the JDK for FreeBSD 5.x, and that I must agree to a very restrictive license in order to download the sources. Next, I can't compile the sources into a redistributable package (because Sun says so, meaning that for every FreeBSD machine that I have I must compile Java manually, nor give Java packages to others), and I can't even look at the sources without being tainted for life. Finally, the compilation takes an extremely long time to finish.
Don't get me wrong. I like what I've heard about OpenOffice. But as long as OpenOffice is encumbered with Java code that requires the Sun JDK, I'm not using it. How many of you know the BSD story when the BSD developers got tired of AT&T due to its licensing (for those of you who don't know, BSD was originally based on AT&T Unix) and started rewriting the "encumbered" portions of their operating system? It would be great if some developers would do the same with the Java portions in OpenOffice.
To elaborate further, I feel that Sun's handling of Java is a nuisance. Java may be a nice language, but as long as its only really complete implementation of it remains licensed the way that it is, I won't code any open source projects with the Java language, and Java is never going to be a primary open source development language. Why should the code that I write be tied to a non-free, restrictively licensed runtime environment that only runs on the platforms that Sun says that it should run on? Python, Ruby, and even Microsoft's own C# (in the form of Mono) isn't encumbered by such restrictive licensing. Sun's slogan for Java was "write once, run everywhere." Well, it depends on what Sun consists of "everywhere." Since the operating system that I choose to use is considered "nowhere" by Sun, well, I guess that Sun's JDK is going to be "nowhere" near my machines again, and for all of the projects that require this JDK, well, I'm sorry, but I'm not installing them, either.
This will be marked as flamebait, but here goes:
Will you people please, please remove the stick up your ass when it comes to Java?
Please?
One of the article's complaints was that "FreeBSD and GNU/Linux for the PowerPC, have no official version of Java." Well, all of the time spent complaining about that has wasted years...YEARS people! The Blackdown folks made Java happen on x86 and amd64 Linux because they did something about it. They applied their minds to working instead of bitching.
Be a proper geek and do the same.
What about BlackDown?
... if you don't like it, write your own replacement that isn't in java.
One has to wonder when some enterprising group will just take the file format code and bung it into open competitors that don't rely on Java. I would prefer the KOffice suite, but LTIC OO.o had the superior MSOffice format functionality.
"As for Java, I am only interested in the subset being promoted by RedHat - the free gcj/classpath variant. Call it FreeJava or whatever, but to me anything else is unacceptable. Come on folks, we came this far insisting on free software, don't give up now over one lousy VM and language spec."
The irony of the F/OSS community willingly accepting binary drivers/firmware while complaining about Java shouldn't be lost on anyone.
Java integrated into the OS would be a terrible thing. I got a Java virus while running Firefox while visiting a website that trades illegal software. (Yes, I guess I do deserve it.)
A NYC lawyer blogs. http://www.chuangblog.com/
This is a beginning of a very good trend, IMO. Linux desktop has to move beyond C/C++ development if it is to compete with Windows. .Net is a loss in that regard, since it will never be quite usable anywhere but on Windows.
So, people starting to use Java on Linux desktop is a great thing. Let's move there faster. Linux has to have an answer when the MS world starts writing majority of client apps in managed code.
I'm among the ones who would rather lose some features than keep being forced to live with something that's big, slow and unfree like Java.
Did anyone consider a fork possible/necessary to get rid of Java and, for example, use free languages as Python or Ruby to write OO.o tools?
The only time I got in an accident my vehicle had 4 wheels, so now I only drive a motorcycle.
On a more serious note: Do you honestly believe that a homegrown macro language would have been any more secure than choosing a language which they know they can get help from the project sponsor on? I would guess that Python was the second choice, and would have been trendier, but they would be more likely to get integration help from Sun than from the Python crew (for financial/marketing reasons, not because of a lack of benevolence on Python's part).
This is not the greatest sig in the world, this is just a tribute.
OOo is open source. You have the power to fork it. Why do I hear so much whining and see no fork?
More Open Source software is written in Java than any other language.
Java is Free enough. If Java had been more free early on, then today, Microsoft would have the dominate proprietary Java implementation, instead of Sun, and it would be specific to Windows only.
"People complain about releases not being quick enough and when Java is used to make the build environment less complicated, people bitch about it not being open source. You can't have your cake and eat it too."
That's assuming that there are no F/OSS solutions that make the development process significently better. In the context of the majority that program, I agree. In the wider context of programming in general, I disagree. In other words there are solutions that the majority haven't adopted, that the minority are productive in.
It truly is insane... I'm grateful, Sun's license does not allow them to bundle in their own Java in too...
In Soviet Washington the swamp drains you.
The usual response to anyone who wants anything included in a F/OSS project is "why dont you do it yourself? The developers do it to scratch their itch not yours"
The developers made a design decision for THEIR project. But oh no, thats no good because it's not what the F/OSS community wanted. Lets get this straight - its their project but they shouldnt use the language of their choice because others dont like it?
They're the developers, they decide what they do with it. Who are you to tell them what they should develop their own product in? So it doesnt conform to YOUR philosophy, so what? Sorry but this certainly smacks of zealotry. If you dont like it then fork it and create your own version of OOo.
Maybe its news to you but .NET is nothing but free.
It may be gratis if you buy the operating system from MS - buts its not in any way free.
Just saying it like it are.
The Java JRE and JDK may be free as in beer, but it isn't free as in speech. Far from it.
The Java JDK and Blackdown is open source, but it is encumbered. What I mean by encumbered is that it is distributed under a very wordy/legalese and restrictive license; read it for yourself to see what I mean. It's almost like an EULA. To make a long story short, it is open sourced, but it's proprietary, too.
the movement is getting too big to keep it together. Why does every single man made orgaanization suffer this fate? Is it all about egos and public displays of power? Definitely impresses the chicks, eh? That's really what it boils down to here. Everything that we accuse the corps of doing, we are going to do ourselves, apparently. Once again, we are proving that we are all the same in every way...All of us. Watch Animal planet for a week. You will see the exact same behavior amongst the chimps. Oh well At least I can say thanks for giving me all this free stuff to play with.
What?
The Qt libraries were free, if not Free, and they made it easier to create an environment and apps that Just Worked. The result was a series of complaints, and when those failed, GNOME. TrollTech noticed that it was losing ground as distros favored Free Software over free software, and finally GPLed Qt.
If OO.o becomes harder and harder to run on GCJ, you're going to see the same thing. Maybe an OO.o fork, maybe a specific effort to create a different Free competitor. But dependence on a non-Free system component is going to create trouble; if OO.o wants to thrive in the long run, it's going to either need to be GCJ-compatible or have Sun open-source Java.
After reading TFA, and then seeing this I asked myself: WTF is Caolan Macnamara, anyway? Select, middle button, enter:
Has OSDL started using /. editors?
Maybe it's a Microsoft ploy to make MS Office run faster under Crossover, than OO.org does natively!
#include <sig.h>
The free implementations will probably be several years behind SUN's implementation. by the time you have version X fully implemented SUN has already introduced versions X+1, X+2 and X+3. I need to constantly fetch stuff from cvs to be able to do even the most trivial homework exercises because Swing support is still partly very weak.
So the issue is that OO is dependent on Java, and the purely Free implementations of the relevant Java support is not ready to be a full standin for the vendor-supplied version.
It seems to me that the problem here is that the Free Java implementations are unready and need to be completed. It doesn't seem to me like the problem is that OO is using Java and needs to use something else.
Sun is hurting themselves and Java by not making it easier to include their JRE in a linux distro. But I find it very odd that people claiming to speak for the free software community seem to be taking the tack that OO should go with what is convenient for the Open Source community, rather than going with what is convenient for OO and letting the open source community write the code to make it convenient for them. This seems to be the opposite of the tack open source software advocates usually take. At least, when it is pointed out that open source software is criticized for inadequate interface quality or user friendliness, this is the claim made-- that if nonprogrammers don't like the interface, they should fix it themselves. Well, if programmers don't like OO's apparent dependence on sun-jre, perhaps they could fix GCJ themselves?
Irritable, left-wing and possibly humorous bumper stickers and t-shirts
The only virus I've ever had infect my Windows computer was Java based
And if you had gotten this virus through a floppy disk, would floppy disks make you nervous? I assume you got this virus over the Internet - are you planning on pulling your network connection?
I don't feel any better about Java being integrated in some way that I don't understand
Ignorance causes fear. Big deal. You can either accept that this is an irrational fear, solve the ignorance, or bow to the fear. The latter is what you are doing. The other options are far better.
Java has a very good security record. Anyway, this java stuff has not to do anything with remote execution, just with application code. The chance that there is a buffer overrun in Java is very small (it would mean a serious bug in the JVM). No software is perfect, but Java has a much better security record than most execution environments out there (compare it for instance with ActiveX).
The problem is that there is little to choose from if you want rapidly developed, secure code. C++ code gets complex very fast, and is difficult to check for memory leaks, buffer overruns etc. PERL and Python are less maintainable. IDE's for Java are getting very easy to use as well. MONO, well, this IS a Sun project...
megacompany 1, meet megacompany 2.
Remember the Microsoft vs. Borland Wars?
The Microsoft vs. IBM wars?
After all these years, the world's still the same.
"FOSS" is spelled out in gigantic, bright yellow letters on the football field of Henry Foss High in Tacoma, WA. You can see it from like 4 miles away. It's annoying.
Disclaimer: I am an OpenOffice.org Mac OS X developer and a founder of the NeoOffice project
One of the biggest problems with Java in OOo is the way that it's being used. Probably the largest volunteer developer community outside of Sun is in the porting project which mostly aims to recompile OOo onto other Unix and Unix-like platforms. Part of the portability lure is that the older architecture of OOo made porting easy; OOo itself has its own internal complete abstraction layers for operating system functionality, windowing, widgets, and the kitchen sink. By simply porting those layers, OOo could run anywhere and even the most obscure Unix variant could have access to a MS Office compatible office suite.
Java breaks that. Why? Not all of the platforms on which previous versions of OOo could be built have any official Java implementation (e.g. Linux/PPC).
Now, Java is no longer optional. Java is actually becoming a requirement not only for running OOo. Some of the build tools are becoming implemented in Java. What's worse, many of these newer Java-dependent features and build tools actually require a specific version of the VM in order to be functional (e.g. reliances on libraries distributed with Java 1.4+).
This choice leave platforms without Java in the cold, but sadly it also leaves platforms with outdated Java VM versions in the cold. I only hope this doesn't further cause headache for some of the intrepid 64 bit porters out there since I don't know of any VM that can be safely embedded in 64 bit apps yet.
Porting developers have raised this issue as far back as 2002 and earlier. There's no excuse for the Sun-dominated engineering of OpenOffice.org to have been ignorant of them. Instead of lowering the bar for the build process, the dependencies have just been injected into core functionality! It's sad when the pleas of some of the most prominent non-Sun volunteers to the project get blissfully ignored by the powers that be.
I don't have a problem with using Java for open source software since, after all, NeoOffice/J is dependent on Java. As NeoOffice/J is focused solely on Mac OS X, however, portability isn't one of the NeoOffice/J goals. For OOo, however, portability used to be one of its strengths and is still one of the strongest development communities within the project that doesn't originate from Sun. It's sad to see decisions made that alienate one of the only vibrant non-Sun communities.
While OOo has built a great community of marketing, translation, support, and evangelization volunteers, there is no substantial core developer community outside of Sun. Alienating the precious little that exists doesn't help the situation either. Unless there is serious effort to build up a non-Sun developer community, the project can only be doomed for failure when Sun cuts their development team (or goes out of business).
ed
I've not shied away from installing OO though, I've used it since Star Office, and OO version 1.0. But only time will tell if having some form of Java integration in OO is going to be it's curse or blessing.
Saskboy's blog is good. 9 out of 10 dentists agree.
An actual virus or an unknown program that you ran on your system?
How exactly would Java be "integrated" into an OS? Do you mean a DE or a WM?
Are you intolerant of intolerant people?
And for what it's worth, as a language it is reasonably "safe" WRT appliation development, in that many of problems C/C++ apps have (buffer overruns etc.) do not exist due to code running on managed environment (same holds true for C#, Python, Perl, VB, etc).
As to your Java virus... that sounds like a hoax to me -- Java applets do not have enough access to create viruses of any kind. So the only way for a virus to exist would be to write a full java app that you'd have to execute, just like any other app.
And once morethe FOSS community illustrates how it kills itself. A free, viable, functioning alternative to Office, and people get upset because it doesn't fit their personal definition of "free" enough.
Get some priorities. Sheesh. Only in this community do these minor issues get blown up into huge flamewars over nothing. "It's not FREE enough!" Who the hell cares, it works and it's free to use!
yeah, and moon is made of cheddar cheese. It's true, I saw it on Fox News.
I hope people will calm down once they see this:
http://www.spindazzle.org/green/index.php?p=43
So people use Java when releasing applications for multiple platforms. What's the big deal? The JRE costs nothing to companies anyways.
.NET to program if you can't get the windows and controls to work on MONO on linux?? GTK runs on Linux and Windows but no Mac support without installing X11. Installing X11 might be a pain for most Mac users, let alone that adds another step and requirement on the Mac side.
Why use
Why do people dislike Java so much? Is it because it takes to much RAM when using Eclipse to program or NetBeans??? Is it because it's not easy enough for people to program?? What the hell??
Java it's free, IDEs for development are free, it runs on Macs, Linux, BSD, Unix, Windows, etc, etc, etc... My point is... WTF??? It's like we say in spanish "peladito y a la boca" can't be any easier to develop for multpiple platforms having all the tools.
I say people are just ging nuts over peanuts.
Your multiplatform programing are belong to us... get it??
Have a good one.
===== "Every head is a different world so don't invade mine you FREAK!" smartSAGA said
"That's because traditionally, with a few notable exceptions, client-side Java apps suck. They're clunky, slow, and they look like arse."
o uml-0.16.1/jws/argouml-en.jnlp
e et.jnlp
e bstart/IDV/idv.jnlp
e desktop.jnlp
d io-full.jnlp
= hosted
Talk about looking a gift horse in the mouth.
Guess I better stop downloading F/OSS software like these.
http://argouml.tigris.org/files/documents/4/0/arg
http://www.johnmunsch.com/projects/HotSheet/HotSh
http://my.unidata.ucar.edu/content/software/idv/w
http://www.crosswire.org/bibledesktop/stable/bibl
http://www.geovistastudio.psu.edu/autobuild/gvstu
http://molo.concord.org/software/
[There's a LOT of java software out there]
http://community.java.net/projects/alpha.csp?only
And the fun thing is that on SuSE, Java Web Start is already set up. Click on the JNLP links and it'll automatically download, and set up (Warning some are large downloads).
When I read the headline I was thinking "Fallout" the game has gone open source and I could play it on my SUSE box. Dang dang dang.
MadOgre.com
This is really a matter of target users. If the target users for OO.o were current Linux users and enthusiasts, then they've made a big mistake. However, they're target audience is more likely to be home users or corporate users. In either case, providing a product that is free but is a strong alternative to MS Office has to be their primary concern. If they offer a thin installer that will include a JRE if needed, then this should not cause problems with home users who are willing to subject themselves to a long download time so that they don't have to fork up $$$ for MS Office. For corporate users, including a JRE on the default desktop image used on all the machines, is trivial. The OO.o developers probably stay awake at night dreaming of a Firefox-like revolution and a market-share approaching 10%. Adding features that will appeal to home and corporate users is probably a better way to achieve this than simply trying to appeal to Free Software advocates and Linux users.
Oddly enough, your cell phone and your 2ghz desktop computer have very little in common other than both being Turing-complete.
News for Nerds. Stuff that Matters? Like hell.
OO.o 2.0 is already working on free JVMs. FC4 is shipping this, along with Eclipse, Tomcat, and a ton of other stuff. We've got jonas running as well, just not quite ready to ship.
I tried OOo 2.0 beta on Windows and was unpleasently surprised. There were *no significant changes* in its ugly-ish user interface (other than it finally supports XP skins and Impress has slide sorter as dockable thingy; actually the ONLY thing i liked in OOo2 is more options in PDF conversion - too bad SWF support is stalling) and it's very bloated. Since it requires Java, especially in the database component/client, it's practically unusable - it devours memory and CPU for event the simplest operations.
Now, this is very bad PR. Consider a company with somewhat older computers and OS+Office (e.g. Win98, Office 97 or 2000) wishing to switch to Linux - that scenario is getting less likely by the day (If said company, for whatever reason (faster? smaller?) chooses FreeBSD, it will have even more problems w/java):
- User interfaces on newer Linux distributions are getting waaaay too memory-hungry (ref: a Slashdot article a while ago about bloat in Gnome)
- OpenOffice.org is getting bloated even faster
Unfortunately, OOo is still the only Open-source product out there that can reasonably understand MS Office file formats.-- Sig down
I can live without the listed features - it's not as if 2.x doesn't work without Java. Some wizards, a new database... Purists can live with the lack of a few features which use Java. This is a non-issue.
The Java stuff is there for those who want it; if you don't want Java, nobody's forcing you to use it - OOo2.x will still work fine without Java.
This is yet another troll for Newsforge pagecounts.
Because they wanted to integrate a Java database, namely HSQLDB, into Open Office they claimed Java was necessary. They should have integrated SQLite instead. SQLite is superior for a number of reasons: 1. it is in the public domain, 2. it is insanely fast, 3. it is ANSI SQL compliant, 4. its memory footprint is 250K, and most importantly, 5. it is written in good ol' C.
Cough *FORK* Cough
As noted here and here, it actually looks like there's been a LOT of progress in getting OpenOffice.org to run on open source software / Free software implementations of Java. Perhaps just make "must run on an open source Java implementation" one of the blocking bugs for OpenOffice.org, and don't ship until it works.
- David A. Wheeler (see my Secure Programming HOWTO)
People also forget that calling software licensed by the GPL as "Free Software" is a complete misnomer.
The GPL is a restrictive license; it requires that any subsequent modifications also be released under the GPL. That is NOT "free," which is defined as "having no obligations or commitments."
To me, "Free Software" means public domain.
So, yes, Sun's Java isn't GPL or Open Source. But it is free to use and distribute. Nobody really cares much beyond that fact.
Could Sun suddenly stop distributing Java and start charging for it? Of course. But you know what? They won't. Because they are not stupid.
We're not as concerned as a company about whether Java is OSS or not, but we are concerned about ease of rollout. If I need a new JRE to run OO2, how does that impact the 250 or so Linux systems I have to roll it out to? What about my handful of Windows users I'm trying to migrate from Office? Will this version of Java play well with the versions of Linux we run? It's a potential nightmare.
The OO.o people had a decision to make about how to build in the new functionality they wanted, and they chose Java for purely technical reasons. You don't like it? Don't use it! Find something else, or make use of the fact that it is open source and fork it.
But stop complaining about it, or acting like they had some obligation to develop their software according to your philosophy. Their project may succeed, or it may fail because of its supporters leaving it--but be content to let it play out without screaming about it.
"Science is a way of trying not to fool yourself." -Richard Feynman
they forgot to mention the other fallout: the one between the developers and the people who like text to appear as they type.
java is slow - John Carmack, Command Keen programmer.
Fork OO.o. The source is out there. Create a Free Software-correct fork of OO.o, call it "Free And Open Office" and go to town. Replace the database module with MySQL or PostgreSQL or whatever database you want. Hack out anything and everything that you don't like. F/OSS sees proprietariness as damage and routes around it.
Knowledge is power. Knowledge shared is power multiplied.
up against the wall, counterrevolutionary!
Sounds like Bruce Byfield is offering to do the development himself.
WWJD? JWRTFM!!!
and the only thing more fun than writing inpossible to use software, is to scream at other people for not being true to your cause
I work with big documents - 500pp. When I load them into Abiword, it takes forever to paginate or something the whole document. I think it also has (or did have) the problem of being able to IMPORT filetypes but not export them again.
With oo.org, I load and I'm just ready to go. I've used oo.org for years and I trust it. Do I want a big, fatter software package? No, but it does what I want without any fuss. I also like OO calc a lot too and my wife uses the presentation program and has no problem presenting the results using powerpoint at conferences.
It's been verified that 99.9% of all OperOffice.org installations are based on Intel/AMD/clones or Motorola/IBM CPUs!
The horror! It's not Open Source!
CC
CKSCIII
[1]
The corporations who are behind the making of this software have never had much use for the communist-smelling values of free software, and it has long just been a matter of time before the leverage appeared with which to pull "open source" software into the realm of the proprietary, where real money can be made.
[2
Secondary features (and therefore, community support, if community feels your soft worth it) will come later, and you're project will involve fast enough (think: the time spend by distro's repackaging without java, or to try a gcj port, won't be a time to help you, but rather a time to hate you're choices).
[3]
Daniel Carrera, community contributor representative on the OpenOffice.org Community Council, says that Base HSQLDB "is the fastest and most feature-complete database available that could be integrated given the very limited resources we have." He adds that OpenOffice.org's C++ core was not altered by the introduction of Base
How do you exspect me to comment on the story, when there is no pictures or screenshots?
Embrace and extend people! The only way to counter is to use real Open Source languages such as Python or stable open standard languages like C or C++.
OpenOffice.org is slow, bloated and uses oodles of RAM. Porting it to Java will not help things! Java on Linux sucks and does not run on all the platforms like Linux for PowerPC. Most distros do not bundle it. Sun's JRE is for all effects closed source software. Alternatives are incomplete and since the train is moving will always be so.
No cheese for you.
"To make a long story short, it is open sourced, but it's proprietary, too."
So are PDF's and Flash.
OS/2 actually wasn't a community porting project. It was killed before OOo was open sourced.
I'm not actually sure why the OS/2 work was dropped by Sun. It was deep sixed after StarDivision got bought out, so it may have been for some corporate reasons. The OS/2 versions of the underlying libraries were still in the old CVS branches, but no one stepped up to maintain them or revise them to the newer code bases. In theory, they could still be resurrected and brought up to SO 6.0/7.0 standards instead of the Odin (?) Win32 emulation that's being used by innotek for their OS/2 variant.
With crazy Java dependencies, however, it may be a bit more difficult now. I believe the last version of Java available for OS/2 was 1.3.1 but may be mistaken.
ed
Rinse, repeat.
Here's a link. It generates XML files with the UI that can be using by Python via libglade.
Besides what they are giving, they are getting in return and 10X as much. Samba? Apache? GNOME?
That's the great thing about open source software (like Open Office), if you don't like something, you can fork the project and make it the way you like it. Don't like Java, feel free to rewrite it in C or C++.
... yes different, but a JRE! The tendency will be to use more Java then shy away from it. Interesting. Maybe it will become what Corel couldn't do way back when.
Scary as it is, you are starting to make me think RMS is right in consistently pushing for the Free Software definition.
Look at their JRE license.
The real issues are:
1) There is not a good enough database written in pure C/C++ as there are in Java: HSQL, Apache Derby
2) There is not a good JVM/runtime packages with an opensource license.
So instead of whining OOo uses some non free component to get more market share and please its users, start helping the gcj, classpath and other projects. When RMS did nto have a Free OS he did not turn to 1940 information handling methods, he started making one.
>"It seems a decision based largely on practical
> considerations -- and with a disregard for the
> consequences for both the rest of the free and
> open source software (FOSS) communities and the
> future of OpenOffice.org itself." This is an issue
> that is not going away."
Uhhhh, more like "This is a high falutin' press
release that will never have a mother fucking
verb".
Peace out.
With all the developers bitching about Java and the fact that it's not free, and considering the fact that there is a massive base of Java users and developers that are friendly to the idea of a *nix system to be won over, they sure do seem to be dragging their feet at getting an up to date free JVM.
Java is one of those things that you CONSTANTLY see ppl in the free software camp bitching about. Why don't they bloody well put their heads together, through their weight behind one of the many free software projects out there that are working on the problem and clean-room reimplement the damn thing if it's such an issue?
Even if they couldn't make a free JVM and call it Java, they could still include it all the distributions configured to drive things like OOo. I can't imagine that an OpenOffice 2.0 Kaffe Edition (or whatever the JVM clone turns out to be called) would be such a big task if everyone stepped up to the plate where the JVM was concerned.
-1 Uncomfortable Truth
Heheh - I love that the acronym would become FOO.org. That ought to win over the geek crowd at least.
Servlet v2.4 container in a single 161KB jar file ? Try Winstone
If only the mono guys were smart enough to realize this....
Besides what they are giving, they are getting in return and 10X as much.
The $500,000,000+ worth of R&D being open sourced in June (OpenSolaris) will help balance things out a little. OpenOffice.org is something like 7.5 million lines of code, too.
-- Microsoft is the most expensive commodity operating system and office suite vendor in the marketplace.
Gambas
As from the summary: "It seems a decision based largely on practical considerations -- and with a disregard for the consequences for both the rest of the free and open source software (FOSS) communities and the future of OpenOffice.org itself."
Problem is that Java is not a practical requirement. Many systems do not having Java already installed. For example, Windows, the largest potential market for OOo, does not ship with Java. Now you have to convince the user to download OOo, and then to go and download Java, and then properly install them both, and in the right order. If the screw up, things mysteriously don't work right, and OOo is garbage in the user's opinion.
If they wanted to do something practical, they could clean up their build tree, name things cleanly, and code uniformly. As an example, if they wanted Base to be Java, then fine code out the whole thing in Java. But to have Writer partially in Java and partially in C++ is quite annoying, and needlessly makes things bigger, slower, and more complicated.
I choose the best language from the set of languages that I know for a given job. I stick with that lanaguage for the project, or I code it over from the beginning in a different language. This is because doing otherwise makes your code harder to maintain, and much harder for someone else to work with to add features.
When something gets used by millions, pissing
away FOSS, speed and footprint for the sake of JAVA
training wheels is just too dumb. There is a
clueless wonder at work here.
Get professional. Do the right thing. Or OO.o
deserves the fork! Duh.
"F/OSS sees proprietariness as damage and routes around it."
Unfortunately they see making money the same way.
Think of where you want to end up. A world with the freedoms of Free Software, or a world of proprietary software? Now ask yourself, how does accepting a proprietary platform bring us closer to a world with the freedoms of Free Software? Each step you take is a step in one of those directions. Step carefully.
What does all this mean for wxWindows? Also, given that Java is repsonsible for some of the UI under the NeoOffice port and that there is no native Mac OS X port, does this mean that the promise of a cross-platform GUI library has been deferred yet again? Or did I misunderstand what the issue was in keeping OO.org on the Mac?
--TIA
Shop as usual. And avoid panic buying.
I don't understand the argument at all... how many C programmers want to make changes to gcc?? What difference it would make for C applications if GCC is open or not?? The Java specifications are open .. anybody is free to come up with a java compiler and run time... what else the FOSS community requires??? Also any linux distribution is free to bundle a free JDK/JRE.
... open source code written in Java far exceeds open source code in any other language .. just go to apache foundation and see how many projects are in java.
Java is the language of choice for more than 50% of developers and to say that FOSS community do not want Java is just slander
Instead of slandering let some FOSS org work on a true JVM and JRE...And to top it, Java is greater than Sun.. IBMs and Oracles make more money from Java than Sun. Java is true progression from C and C++. If you turn blind eye to Java, it means you are blind to technology.
A likely outcome of this is that Red Hat (and others?) will put more effort into GCJ. So if the result of OO.o relying more on java is the free software community getting a better Java compiler, that is splendid.
And that's the problem with the FOSS zealots. They always see the perfect as the enemy of the good. Too often when given a choice between something that works and something that doesn't, they choose the one that doesn't.
I don't run Linux to run a non-free operating system, and I find OpenOffice to be a vital part of my distribution. Java, I'm afraid, is not open. A reliance on Java is not a good thing, even if the Java bindings for UNO are much cleaner than the C++ counterparts.
XML is like violence. If it doesn't solve the problem, use more.
Also, since Sun's JRE stops you from including competing products, disties like RH and SuSE will not be able to include it.
This could kill off OO.o.
is looking interesting
I have been reading here on slashdot since a few days ago mentions of java virus(es), but I haven't actually read anyone mention of such a virus's name or what it does. Could somebody expand on this? Are these viruses applets that take advantage of a security hole in a browser's JVM [Sun's or MS's]? Are people finding plain malware or do they actually replicate by infecting executables?
A. .NET IS Java (1.3) Numerous lawsuits were filed, some lost, some won, but ultimately, Microsoft is still producing .NET
Wrong. Very, very wrong. The lawsuits were about MS distributing an incompatable version of the JVM with windows only extention. .Net takes (steals?) lots of ideas from Java, but it is most definately not Java.
As for which is the most "free", neither really, although both have unoffical free versions.
Isnt this the point about open source ? if there is something you dont like or feel could be done better another way - just take the code, fork it if neccessary and do it your own way.
Personally I agree - i'd rather OpenOffice did not have a strong dependancy for Java but thats just me!
Electronic Music Made Using Linux http://soundcloud.com/polyp
They're trojans really, not viruses, as they do not spread themselves, usually they act as a vector for installing malware. The most common one takes advantage of a bytecode verifier bug in the MS JVM, which Sun allowed MS to patch in release 3012 (distributed as a critical update to Windows since about 2 years ago), despite being ordered by a court not to continue to release updates to their JVM.
There was a vulnerability with 1.4.2_04 (or maybe _05?) and earlier JVMs recently, but I have yet to see an exploit in the wild. People are probably becoming alarmed because their virus detection is picking up a "virus", since the exploit code was downloaded from a porn or warez site they visited, but if they are running an up to date JVM, then the exploit code was not executed, so its mere presence in the cache is not cause for concern in itself.
>.NET is also much less mature (as in 5 years behind) than Java at this point,
Hm, well its safe to say then, that you'd better use a serial dialup to the internet than a 100 mbit connection, since the serial dialup is much older and therefore much more mature!
Have you ever thought about the concept 'learn from other people's accomplishments and mistakes, then improve upon that' ?
for those of you who care to read this.
the only permanence in existence, is the impermanence of existence.
Before I get flamed for giving inaccurate info, I don't know where I got 3012 from, it should be 3810.
I think no one has thought about the implication of this.
What does the Knoppix developers think?, I think it is a major concern now because is widely used to introduce people to linux.
If People need to install JRE to properly run OOo, then it may not come preinstalled in Knoppix (if they chose not to include it), and OOo would not be an "Out of the box" program for Knoppix (not for at least some of the features like the DB).
And also, if they chose not to include it, then OOo user base will decrease considerably.
Ubuntu is an African word meaning 'I can't configure Debian'
Back in the old days, everyone used to write free software on Sun's SunOS/Solaris, becuase it was pretty good, and came with a pretty good, free as in beer C compiler toolchain. And then someone at Sun figured they should charge money for the development tools.
Oops. Enter gcc :)
It has happened before with Sun, why should it not happen again? It's a company, companies are greedy by definition. If there is more money to be made by selling Java runtimes and development tools, rather than by giving them away gratis, be sure Sun will not hesitate to do that. They are obliged to care for their bottom line to their share holders. They are not obliged to give stuff away for free if they can sell it.
cheers, dalibor topic
Since OO.org can already make an ODBC connection to MySQL and PostgreSQL to do merges and basic database manipulations within OO.org, requiring Java so one can use an "Access-like" database seems like an effort to provide less with more.
Better be a good database solution and, more critically, better not break current database connectivity with quality servers.
If Sun is going to purposely leverage java dependancies into OO simply because they can, then f#ck them. Take the codebase that is available, strip the java, and offer an alternative. It worked for Xorg.
Join the Slashcott! Feb 10 thru Feb 17!
I would like to see OpenOffice.org become 100% pure Java.
By the same token, I would like to see KOffice read and write MS formats better. That way, on machines where I run KDE I can have a quick-loading office suite that does what I need, and on systems where I have no good alternatives (Windows), I'll have a fully Java office suite that won't destabilize the registry.
Retired from software... maybe. Sort of.
RedHat brings open source further by making java open source.
FC4 whil have several open source java programs, but no Sun Java. Why? Because RedHat cares about their customers future.
It is better than Linux at some things and Linux is better than it at some other things. None are things that really matter.
OpenOffice.org was the most interesting project Sun had and was a banner project for them to prove their good intentions on the Open Source segment. Now they have tainted it.
Caolan is the one doing the porting, so he knows what he's talking about...
Is that GCJ will be improved to the point that it can compete with Sun's JDK/JRE. That would truly be the best possible solution.
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
Haven't you heard?
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
Dictum: all Java code must bw ported to its C# equivalent, through Mono.
Can't this Java code be migrated to Mono?
I wonder, since C# and java are so similar, if all the Java code could be replaced by C# code? Thuis would boost Mono greatly, too, as a side effect.
I beg to differ...
In the Visual Studio editor, you can press Alt and click + drag to do rectangular select, and then Cut & Paste. This is like MS Word and most other similar Microsoft text editors. Just because you don't know it doesn't mean it doesn't exist.
And then there's the Ctrl + Left and Right Arrow keys to go from word to word (and shift to select the words). And then Ctrl + Home / End to go to beginning and end of the code. And Ctrl + Up Arrow and Ctrl + Down Arrow to move between paragraphs.
There are definitely free plugins to VS to work with Trac Subversion, and CVS, as well as the built-in Source Safe compatability.
I'm sure the black on green or some wacky color combination when using VIM on your 32-bit color 17" LCD monitor makes a lot of sense.
This sig donated to Pater. Long live
This problem is much more simple than it appears.
How many applications use built in scripting languages? Especially among those that are more complex. GnuCash comes to mind, but there are others.
The issue is not it's dependance on Java, but that it's not using a free Java compiler.
The article seems to confuse the issue however. I suspect there are ulterior motives behind this _Newsforge_ article....
Looks like a chance for KOffice.
Considering that Qt is about to be GPLed for Windows...
Any more questions?
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
I said:
Now, unless you can prove that statement to be incorrect by stating usage statistics for LinuxBIOS, I think the point still stands. Anyway, to use and support LinuxBIOS is merely to fragment the user and developer communities for an open BIOS project - seeing as one (IEEE1275) already exists, is very stable and widely adopted.
Man, it's so hard to take you seriously when it's obvious you have NO CLUE what you're talking about.
Microsoft's Java = Java 1.1
Java 2 == Java 1.2, 1.3, and 1.4
Java 5 == Java 1.5
Java has become so bloated and complicated that it's infeasible that any FOSS implementation will ever be made that supports even a small percentage of software.
YES!!!
Have you to pay by using VBasic Runtime (TM) in the e-commerce? :(
YES!!!
Have you to pay by using GCC's C++ in the e-commerce? :)
NO!!!
So, i did pick up GCC's C++.
I hate Java (tm), VB (tm), .. fuck you Sun, M$, ..
Actually, there are more stupid licensal reasons than technical reasons.
open4free ©
the reality is that unless SUN decided to make binaries available for a platform with an end-user license, there is no practical way of getting JAVA on a machine.
Wrong. You confuse Java the language with Java the platform. gcc compiles Java source down to native machine code on most architectures and provides its own runtime for the parts of the system which require it. If you want to run Java bytecode (either compiled with gcc or some other Java compiler) you have a joice of Java Virtual Machines and Java Runtime Environments from sever manufacturers, including IBM.
Now, SUN of course has such binaries for Windows, Solaris and Linux and some other systems, but for example not for FreeBSD/OpenBSD.
FreeBSD and OpenBSD run Linux binaries very well. Native ports to these platforms are not required. Incidentally, Solaris 10 will also run Linux binaries unmodified on x86.
First of all, few Linux distributions seem to have managed to include a JAVA runtime environment at all, in all other cases I have to download it from SUN. More problematic however is that when maintaining a Linux machine, you may end up having to install newer versions of libraries, which at times introduces compatibility issues. It is however not trivial to just recompile JAVA and link against the new libraries.
Well, I use Slackware and that comes with an up-to-date Sun Java Runtime Environment. Installing a JRE (or SDK) is not very difficult, and is rearely more complicated than extracting a tarball as root and setting some environmnet variables. As for recompiling Java to run against "new libraries" you completely miss the point of Java. The new JREs are backwards compatible.
Failure to do so may result in one or both of two things:
* An alternative Open Source JAVA gets created over time
* JAVA becomes irrelevant
Unless you have been living under a rock, you will realise that there are several independent Java implementations available, including ones from Sun and IBM, a free one called kaffe, and of course gcc's java compiler. Java will not become irrelevant. There are billions of computing devices around the world running Java. What might happen is that Miguel's anti Java/pro .NET FUD might become a mindset amongst the /. zealots. (Might? I think it already has).
The recent settlement between SUN and Microsoft doesn't bode well
No, not for Microsoft. As usual, they're doing a good job of shooting themselves in the foot.
Anyway, your article sucks.
Stick Men
For many years, we had both compiled and scripted languages. Compiled ones had performance, and scripted ones had portability. Unfortunately for the likes of Sun, scripts are also generally written in human-readible text (except Perl, but that is another story, just kidding). So if a company wants to release a program without the source code, they compile it. Then they are limited to one platform.
Java doesn't offer anything new in the "Write once, run anywhere" department. Perl has been doing this for a long time, as have other scripting languages. What it does do is offer a "Compile once, run anywhere," so that commercial software houses can offer closed source software with the opaqueness of compiled programs and the portability of scripting languages.
This is why I believe that languages like Java and C# will eventually fall to the likes of Perl and Python. As open source marches forward, it takes away any benefit that Java has and hands it to these scripting languages.
LedgerSMB: Open source Accounting/ERP
May I kindly instruct you to educate yourself using the http://www.opensource.org/licenses/ site that lists all the OSI certified open source licenses? I especially kindly would like to point your attention to the fact that there is no SCSL listed there. And that's not an omission. :)
Furthermore, may I kindly instruct you to enlighten yourself reading the fascinating insight into the reasons why Sun made the SCSL the way they did it on http://www.sun.com/981208/scsl/principles.html , which clearly spells out that SCSL is supposed to combine aspects of 'Open Source' and 'Proprietary' licensing models into one. That's should be a very huge clue bait that it's not open source. The document also gives some explanation why Sun explicitely didn't want an Open Source license.
If you feel the need to educate yourself on the specifics of what makes the SCSL such a funny read, I kindly refer you to http://advogato.org/person/robilad/diary.html?star t=46
which compares the SCSL versus the Open Source definition, and finds it violating 8 out of 10 principles. The SCSL is about as open source as Microsoft Windows 98 SE EULA, I guess.
cheers, dalibor topic
OK, you are right about the SCSL - it is not truly open source.
But, I am afraid my honest reaction is 'so what?'
I simply don't feel the need to stick to the high principles of open source all the time. I base the software and systems I use on decades of experience of dealing with companies. I have dealt with both Sun and Microsoft over a very long time, and Sun has always been trustworthy, and has donated huge amounts of source code (under licenses you would probably approve of) to developers. Microsoft, on the other hand, has been problematic, and I find comparisons between Sun and Microsoft to be simplistic and mistaken.
We all make compromises. You are probably using an open source system, but it is running on a proprietary processor in proprietary hardware. However, with those aspects you have choice. Same with Java. Sun's code may be non-GPL (or any other OSI license), but Java is available from many vendors - you have a choice. My view is that not using it because of license objections is to seriously restrict your choice of development language without much reason. I'm sure you have a different view!
You don't have to believe it. You can go ahead and check it out yourself by getting the simple BigInteger benchmark from i2p at http://dev.i2p.net/javadoc/net/i2p/util/NativeBigI nteger.html
They also use GNU MP and have a factor of 10 improvement over Sun's code on their data. Running the benchmark on Kaffe from CVS head with -Xnative-big-math makes kaffe run about 4 times faster than 1.4.2 on the modPow tests. Which is why, in scientific and crypto intensive applications, you may want to use Kaffe rather then Sun's implementation.
cheers, dalibor topic
Nothing really. I'm pretty amused by desperate attempts by Sun's marketing division to rub off a bit of 'Open Source' street-credibility onto their proprietary product by calling it 'as good as open source', 'closed open source' and what not. It's an amusing running gag in the 'Java melodrama'. I think 'closed open source' is so far the funniest description I've ever heard of Sun's licensing policy, and it comes right from Gosling.
That being said, just because Sun's implementation is not available under a suitable license, doesn't mean that Java is bad or useless or something. It's a cute platform, as C-based platforms go.
Like RMS said, let's build up implementations that help make software written in the Java programming language accessible to more people without getting them entangled in bogus non-free licensing agreements. The restrictive choice of licensing means that people who care will write implementations like gcj, Kaffe, IKVM etc. that are (becoming) better in most respects, not just freedom, than the non-free offers. It may take a few more years, still, but it's been happening already at an amazing pace. This whole article shows how misinformed people are about the massive amount of progress being made on free software implementations: OOo is now buildable with gcj thanks to Caolan, and most of the things work.
What license Sun choses for their J2SE code is completely irrelevant these days. Sun had the chance to open up their software while their implementation still mattered, people were begging them to, now the begging phase is over, and for an increasing number of people the future of the platform is beggining to lie in GNU Classpath. And they are taking an active part in shaping that future by contributing to it.
Sun is now, belatedly, trying hard to emulate GNU Classpath and Kaffe and build up communities around their code base. Looking at Sun's history of 'proprietary-to-open' transitions in OOo and NetBeans, I doubt they will succeed before Kaffe passes the TCK, in particular as long as they stick to their cooperation-unfriendly licensing regime.:)
cheers, dalibor topic
That's J2EE. I asked for proof that Sun's VM passes all the tests. That's J2SE. They are very, very different things.
If you want to prove it to yourself. Here is the website for some test suites: http://java.sun.com/developer/technicalArticles/JC Ptools/
That's just a link to a description of the testing tools. It's not the tools, nor is it the J2SE test suite. Everyone can put up a cute web page saying they are compatible with something, but hardly anyone can actually prove it. And without proof, such claims are worthless.
Why should I care?
Because it's pointless to argue about compatibility without knowing what it is, and having means to verify it. You made the assertion that Kaffe is incompatible, but you can't even prove that Sun is compatible. So what's your point about invoking that marketing nosense? The branding program is just a way for Sun and their business partners to market themselves together, as far as I can see. It has nothing to do with real, verifiable compatibility.
It's like a cargo cult: just because it has a coffee cup logo on it, it must automatically be compatible. Yeah, right :) Microsoft's VM had red coffee cups slapped on it, too, and that didn't seem to work that well for guaranteeing compatibility.
cheers, dalibor topic
Man, it's so hard to take you seriously
;)
This is slashdot, who said I was even taking myself seriously?
As for a FOSS JVM that runs programs, really they only need to run 3. lime wire, azureus, and oo.org
If you can do that, then all is happy and good right?
Like RMS said, let's build up implementations that help make software written in the Java programming language accessible to more people without getting them entangled in bogus non-free licensing agreements.
I support this project, but I'm afraid I just don't care about these so-called 'bogus' licenses. Java is Sun's product. They can do what they like with it. I'm grateful they provide it for no charge and allow me to re-distribute JREs with my apps. That is all I (and thousands of other developers) need. I think calling arrangements like this 'bogus' is rather petty and mean-spirited. Few companies have provided products like Java free of charge to the developer community.
Sun is now, belatedly, trying hard to emulate GNU Classpath and Kaffe and build up communities around their code base. Looking at Sun's history of 'proprietary-to-open' transitions in OOo and NetBeans, I doubt they will succeed before Kaffe passes the TCK, in particular as long as they stick to their cooperation-unfriendly licensing regime.:)
I really don't get this attitude to Sun. Stuff that they have released like OOo have been vital for the acceptance of Linux on the desktop. They have done so much good for the IT industry over the years.
I am (as you know) no expert on licensing, but they do now have OSI-approved licenses, like the one for Solaris 10. It is possible to label many OS licenses as 'cooperation-unfriendly', even the GPL! The licenses have different purposes.
As for the TCK, I wish Kaffe luck and hope it does get to be a compatible implementation. The Kaffe you have described seems a huge improvement on what I remember of it years ago!
Because it's pointless to argue about compatibility without knowing what it is, and having means to verify it. You made the assertion that Kaffe is incompatible, but you can't even prove that Sun is compatible. So what's your point about invoking that marketing nosense? The branding program is just a way for Sun and their business partners to market themselves together, as far as I can see. It has nothing to do with real, verifiable compatibility.
No. It is to do with the practical ability to move code between VMs and JREs. The 'Java' brand indicates that you can do this. I don't know how to prove that Sun's VM passes the test, but I know that it does. Why? Because thousands of developers rely on the compatibility, and it works. You can label it 'marketing' if you like, but that does not remove its practical effectiveness. If it did not work, this would be a major news story and Java's reputation would crumble.
Anyone who wants to test any part of Java can join the JCP (it is free) and download the test tools.
It was not just me who said that Kaffe was incompatible - just take a look at that benchmark page:
http://www.shudo.net/jit/perf/
"Kaffe does not work correctly with the applet version of SPEC JVM98". That is just one example.
However, I have just seen a screenshot of Kaffe running Eclipse - that is impressive! But, as a commercial developer, I need that Java brand. I need to be able to guarantee (or at least foolishly believe that Sun guarantees) that the Java implementation will run my apps with no code changes and no problems. I can't risk putting major enterprise apps on Kaffe and just hope; no matter the quality of the coding.
Yeah, right :) Try compiling a HalloWorld app on 1.5 and running it on 1.4. Both have the cute logo. But the same program compiled on one, won't necessarily run on the other, unless you somehow manage to convince the compiler to generate code with the other VM's class file format version information and to avoid stuffing in references to the 1.5-specific classes into the class file.
As far as I can see from the logo image, it contains no 'versioning' information, so it's useless for that scenario.
I don't know how to prove that Sun's VM passes the test, but I know that it does.
As a scientist, you surely know that's belief, not knowledge. I told you it's a cargo cult :)
If it did not work, this would be a major news story and Java's reputation would crumble.
Hardly. Sun has regularly been making changes to each release so far breaking backwards compatibility at the source level(the assert keyword, JDBC 3.0 breaking interfaces, etc.) and even at binary level (the System.getenv() melodrama, see http://www.tigress.co.uk/rmy/java/getenv/case.html for an overview). And guess what? Most of Sun's users just kept swallowing the breakage and loved it, because they never noticed it happen. Others vented their anger on BugParade without much result. Where was the big news story? :)
Sun has pretty much forked Java since 1.2 in interesting, slightly incompatible ways, and never documented properly what changes they made to the VM and Language specification, so that a lot of people implementing free runtimes are forced to scratch together information from various crumbles on mailing lists. Noticed any of that in the news? Of course not, because for most users it doesn't matter at all. Most users couldn't care less if their perception of Sun's stewardship of Java and reality matched. They are locked in into non-free software, so why bother getting disillusioned :)
I can't risk putting major enterprise apps on Kaffe and just hope; no matter the quality of the coding.
I fully agree. That's what the test suites of those major enterprise apps are for. I think Jonas on gcj is getting really good, afair from aph's posts on the gcj lists.
Don't trust claims blindly, check them for yourself. Be an informed customer.
cheers, dalibor topic
Yeah, right :) Try compiling a HalloWorld app on 1.5 and running it on 1.4. Both have the cute logo. But the same program compiled on one, won't necessarily run on the other, unless you somehow manage to convince the compiler to generate code with the other VM's class file format version information and to avoid stuffing in references to the 1.5-specific classes into the class file.
:)
This is a very poor argument. Compatibility does not have to be backwards. I would not expect one program compiled with a later version of libc to run with an earlier one. I would not expect an application that ran on Linux 2.6.x to run on 2.0.x. If someone says I need a Java 1.5.x JRE, that is fine by me. I'll get any 'Java'-labelled JRE of the same number from any vendor on any platform and my application will almost certainly work with few problems. Sure, things are never perfect, but compared to the C++ coding days...
And guess what? Most of Sun's users just kept swallowing the breakage and loved it, because they never noticed it happen.
Exactly. We never noticed it. We took large applications like Tomcat and JBoss and put them on Sun's VM on Windows and they ran fine, then we put them on IBM's VM on Linux and they ran fine. We never noticed it.
They are locked in into non-free software, so why bother getting disillusioned
If you choose a particular language you are locked into it after a while, free or not. I have had decades of dealing with incompatibilities in implementations of supposedly the same language - C, C++, Smalltalk - Java is one of the best things to have happened in software development for a very long time.
Don't trust claims blindly, check them for yourself. Be an informed customer.
This is rather condescending. Why are you assuming I am not checking them for myself? I am not naive enough to expect perfection, and if I move to another vendor's VM, I am going to be a little cautious. I know full well that there are going to be some niggling problems. However, something without the 'Java' label, indicating a TCK pass, is not going anywhere near my commercial servers.
I have had the pleasure to read the SCSL a few times, to enjoy its full literary value. Some of the provisions in the SCSL are very interesting attempts to extend copyright without regard for copyrightability, others are pretty bold attempts to grab patent-like protection without going through the patent process. That may have been just funny back in 1999. These days, after SCO has shown how much expensive mess a rogue 'copyright holder' can do without even owning copyrights, and having such privileges written down in their licenses, I think it's justifiable to call licenses explicitely grabbing such wide privileges dangerous, or more mildly, 'bogus'.
I really don't get this attitude to Sun. Stuff that they have released like OOo have been vital for the acceptance of Linux on the desktop. They have done so much good for the IT industry over the years.
Sun is a respected member of free software community, and does a lot of things that are just plain great. They also do a few things that are not that great. That's understandable, it's a company after all, it's not a charity.
Sun's choice of licensing their Java technology implementations is their own business. A critique of some of Sun's licensing choices does not imply critique of Sun's other actions.
For example, JCP is a great idea. The execution is not that great though, the specifications coming out of it in the J2SE area have over the years decreased in quality, in my opinion. The JLS3 has stil not been released as a final specification, *years* after the assert keyword was added to the language.
As a Sun Java user, you may chose to interpret that as an attack on Sun, without undertaking the effort to validate my assertion against facts, instead validating them against your beliefs. That's fine. It's a human, emotional response. But as you may have noticed during the course of our discussion, I have made several assertions that you believed to be untrue, that have in fact turned out to be somewhat contrary to your initial beliefs.
There is a difference between what you believe to be true, and what is true. I call SCSL cooperation unfriendly not because I have a bad attitude towards Sun, but because Sun themselves are changing away from the SCSL for JINI, another 'crown jewel' technology in Sun's crown, in order to encourage further adoption, remove restrictions on user code licensing, and to fix issues with commercial multi-tiered distribution. See http://community.jini.org/servlets/ReadMsg?list=di scuss&msgNo=1182
They are switching to ASL2.0, btw. See http://community.jini.org/servlets/ReadMsg?list=di scuss&msgNo=1404 for details.
cheers, dalibor topic
But as you may have noticed during the course of our discussion, I have made several assertions that you believed to be untrue, that have in fact turned out to be somewhat contrary to your initial beliefs.
Only one. The Open Source nature of the SCSL. On other matters I remain resolutely unconvinced. I see little evidence that Kaffe is either fast or compatible enough for general use. I am a Debian user, and if I try and install almost anything Java-based I seem to end up with Kaffe installed as the default JVM on the path. I can usually tell this because of the strange exceptions that appear when I try and use most of my Java applications! (And no, they are not all Java 1.5 compiled)
Obviously. But I wasn't the one claiming that the logo implies compatiblity, that was you. And the logo looks just the same on all implementations, afaik.:)
So what is it now, does the logo or doesn't it mean that implementations are compatible?
For another intersting bit of information that you seem to be missing, there is no backwards compatibility between 'point-releases' of a Sun implementation either. See http://java.sun.com/j2se/1.4.2/compatibility.html# incompatibilities .
Why are you assuming I am not checking them for myself?
Because you believe that Sun's implementation is compatible, but you don't know it and refuse to check. Instead you voluntarily chose to rely on hearsay. You defend relying on hearsay, saying that it doesn't matter for you because you don't implement VMs, which I find pretty amusing, as in another breath you say:
However, something without the 'Java' label, indicating a TCK pass, is not going anywhere near my commercial servers.
That's pretty funny, as you don't seem to really know what the Java label indicates, have not seen the test suites, and apparently have an idea of compatibility that James Gosling makes jokes about in interviews[1].
What I find really fascinating is that Sun released 1.4.2 with a known compatibility test suite failure according to the page I quoted above. So much for the logo guaranteeing passing the test suite, I guess.
cheers, dalibor topic
[1] 'Well, I tested it myself and it seems to work OK for me,' or 'Hi, a bunch of my friends tested it and it worked OK.' See http://programming.itmanagersjournal.com/programmi ng/05/03/17/0131245.shtml?tid=56
If you read my posts carefully, you'll notice that I did not make those claims. You're bashing a straw man of your own making. I hope it feels good, it's surely amusing to watch from over here.
I said that for some specific uses, Kaffe is faster than Sun's implementation, and showed you how to check it for yourself, and explained why that is the case.
I also questioned your claim that Kaffe is incompatible by showing that you do not have any knowledge about compatibility. You have a lot of beliefs about compatibility, but no way to prove them, and that sort of disqualifies your qualifying assertions because you don't really seem to understand what you're talking about.:)
I explicitely did not say that Kaffe is compatible. It will pass the TCK one day, but till then, I can not verifyably tell how much, or if it is compatible at all, so any such assertion is pointless.
If you have problems with Kaffe in Debian, you're kindly invited to use Debian's bug reporting mechanisms. I'd recommend bug-buddy.
Also, on a side note, since you pride yourself on using a 'Java' branded release of Sun's non-free software and assume that means something, I'd like to kindly point out that what you're using has never been certified as passing the TCK on any Debian release. So what you're running is not 'Java'-compatible in any meaningful, verified way.
You're apparently blindly trusting a logo to shield you away from libc & kernel issues and you sound as if you like it that way. Good luck, anyway, you sound like you may need it. :)
cheers, dalibor topic
I also questioned your claim that Kaffe is incompatible by showing that you do not have any knowledge about compatibility.
This is logical nonsense. Questioning Sun's JVM compatibility, (for whatever political reasons you have) does not make Kaffe any less incompatible!
Also, on a side note, since you pride yourself on using a 'Java' branded release of Sun's non-free software and assume that means something, I'd like to kindly point out that what you're using has never been certified as passing the TCK on any Debian release. So what you're running is not 'Java'-compatible in any meaningful, verified way.
Then there is not much use having it installed along with stuff labelled 'Java' is there? I wonder who suggested it might be a valid replacement?
You're apparently blindly trusting a logo to shield you away from libc & kernel issues and you sound as if you like it that way.
Neat the way you condescendingly assume that I am blindly doing things!
For years Java HAS shielded me from libc and kernel issues. It works; it works day in and day out for thousands of developers. I transfer projects consisting of hundreds of thousands of lines of Java code from one OS to another and one Linux distro to another with no problems at all.
You know that being condescending isn't helping your case! I admire the effort being put into Kaffe, but ranting zealotry and being so patronising to anyone who disagrees with you is perhaps not the best way to encourage its use.
I'll take a look at Kaffe in a year or so, to see if it has matured. I am prepared to take interest in a product despite the attitude of its supporters.
That must have been a misunderstanding. I questioned the soundness and usefulness of a definition of compatibility that is based on belief, rather than on verifiable proofs.
Without being able to prove whether an implementation is compatible or not, one can not (scientifically :) decide assertions of compatibility.
I am prepared to take interest in a product despite the attitude of its supporters. Cool! See you around. And I hope you don't mind me being zealous about compatibility.
cheers, dalibor topic
When Linus started Linux he made it GPL'd. He said that it would aim towards POSIX (and other standards) compliance. The Open Group controls the Unix standards and gets to decide who calls what "Unix" (look at Apple's trouble). Linux can not be called "Unix" since it hasn't been validated. More specifically, every time it is modified, it would have to be revalidated to conform to the spec AFAIK, and not just the Linux kernel. It's more involved than that.
After Apple OS X, Linux is probably the most widely deployed Unix-like OS on the planet.
Sun is now open-sourcing Solaris to try to compete with Linux, to rejuvenate the Solaris community and to get more developers involved in Solaris and software to run on Solaris. Solaris is still 5 years ahead of Linux in many areas.
Now, if someone had developed a JVM in all but name (unable to call it "Java" for branding reasons), GPL'd it and said that it aimed towards Java compliance...
Just another thought.
It really is annoying not being able to redistribute those binaries that you've made. Keep shouting, but shout at the right people. They are listening, but big ships take time to turn.
Stick Men