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.
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
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.
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
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...
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...
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?
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.
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
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.
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.
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.
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!!!!
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.
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?
My first grammer nazi reply!
:-)
*cough*
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.
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
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
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.
Correction, he rips J2ME a new one.
The problem with J2ME is that phone companies have been adding their "extras" onto the platform or worse, not making them fulling compliant. Samsung's major HTTP screwup on the A500 is a great example of that.
As for Java being slow... give me a damn break. It's running on a PHONE!
So of the rest of that article, particularly the "no memset" and " the inability to read resources into anything but a char array" so a complete lack of understanding.
Blaming a language on a bad implementation of a JVM on a phone is just stupid.
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.
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.
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.
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...
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
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!
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
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
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.
How do you exspect me to comment on the story, when there is no pictures or screenshots?
Here's a link. It generates XML files with the UI that can be using by Python via libglade.
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.
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
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.
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.