
"Lining up against"
Not sure that's the best way of putting it unless you know that they won't allow their code changes to be merged into LibreOffice.
IBM's putting its weight behind an Oracle-backed OpenOffice push rather than follow Google, Red Hat and others on an independent effort. The latest version of IBM's Symphony collaboration suite, version 3.0.1, will likely be the last based on the computing and services giant's fork of the OpenOffice code base. IBM is instead …
As long as OO is under Apache software license, LO crowd can use any improvement or contribution comes with it ( while the other way around is not possible). When IBM will take OO and release a proprietary version of it, they will be under no obligation of contributing back. Actually this is why IBM prefers to use OO instead of LO. The Apache license allows them to benefit from the community contribution without the obligation of giving back which is quite cool isn't it?.
Anyway, as long as OO and LO both adheres to ODF standards we all have nothing to lose.
Releasing their way to irrelevance: LibreOffice 3.4.0 was released last June, 3.5 is slated to be out next week, and 3.6 by August.
I'm sure I read that the ponderous release schedule was bugging many of the developers, back at the time of the schism. It certainly seems that the LibO devs have managed to up their game.
Er, do you seriously consider that because they have the same version number, openoffice 3.4 and libreoffice 3.4 are the same? Hasn't the new firefox schedule taught people how little numbers mean? openoffice might be irrelevant, I don't know, but it certainly isn't a version number that proves it.
No, I certainly don't expect that OO 3.4 will be the same as LO 3.4, mainly because of the licensing situation.
Any features in OO 3.4 could be imported into LO 3.4; the reverse is not true (and was not true from back when the go-OO fork was born, and used by many Linux distros).
So, no, a version number in and of itself doesn't prove it - it's the version number coupled with even the mildest notion of what has been going on in both camps.
ALL that money and effort poured into Symphony could have been spent paying off those "unfindable" orginal patent holders, the existence of yet unfindability of whom purportedly makes it unsafe for IBM to just update Smart Suite.
Looks like I'll be consigned to using Lotus Smart Suite as a has-been, lame database app protytype rather than a go-to tool.
Sucks to be in this position.
OO has some nice things in it, but it is just plain old jarring, stressful, and STILL lacks the ability to EASILY do what Lotus Approach can do. Unfortunately, Smart Suite has not seen a worthwhile new update since, what, 2004, of not 1999?