I prefer OpenOffice
over LibreOffice. Why? Because it seems smother, easier to use than LibreOffice.
I have both on my computers and only use LibreOffice, when I need to, on certain, newer MS Word/Excel documents I receive from others.
Apache OpenOffice, sized for euthanasia by one of its own last year, still lives and should see an update before the end of May, allegedly. The open-source productivity suite has been referred to as "a shambling corpse" by those appalled at its languid update schedule and those skeptical that its skeleton crew of volunteers …
@ITS Retired
Interesting experience. oOo uses its own font rendering library and LO uses, since version 5 I think, the native library on the OS it is running on. Information about your OS and graphics driver would help pin that one down.
Concrete example: ancient Thinkpad X61s, intel graphics, intel open source driver under Slackware 14.2 with stock KDE, I could see a response difference between oOo installed from the Apache rpms on the one hand and the Alien Bob LO binaries/version built from source on the other.
Pint to all involved with both projects. I use them almost every day.
I prefer LibreOffice over OpenOffice. Because it's receiving active development new features and bug fixes for the past several years that OO hasn't.
I think the name LibreOffice is horrible though. It would be nice some day if it could reclaim the use of the name OpenOffice.
LibreOffice (and OpenOffice assuming it ever develops) really need to start thinking about the future though, especially cloud storage and other forms of online integration. Microsoft are really pushing this hard to lock people into Office 365 so it would be good for LibreOffice to offer something analogous for businesses that want to get out. 5.3 has an "online" collaborative mode so that would be a good thing to expand and push the benefits of.
If something is good then there is no need to lock people in. MS has already demonstrated that your storage allocation may go down as well as up.
If ephemeral storage (that's what cloud storage should really be called) is needed then let that be provided by a third-party that makes available hooks for all products, including maybe {O36x|x<5}
Apart from "core competency" considerations, Integrating cloud into LibreOffice, and integrating cloud into OpenOffice using a different technique forces people into making a committed choice. If the projects were ever to merge then this would be a barrier to merging.
P.S. I prefer OO because I started using that first, but I have both on my system.
> LibreOffice (and OpenOffice assuming it ever develops) really need to start thinking about the future though, especially cloud storage and other forms of online integration
No. An office suite is an office suite, and the storage problem is quite orthogonal to it.
And with that said, there are more than a few "cloud storage" solutions to choose from. At our organisation, it is Nextcloud with locally installed desktop (and phone) clients, which makes the "cloud storage" part of the equation transparent to users. That is just an example though, and many other solutions are possible, none of which are tied to the office suite vendor.
Develop the code to run LibreOffice (or even OpenOffice, merge the damn projects already) and simply publish it to the world. Now everyone can run an online office suite on their own servers, or on any of the thousands of providers that will inevitably appear. The benefits of online without the lock-in.
The benefits of online without the security
Apologies for being negative.
Opensource has lots of benefits, but consumers of it have to be savvy about the ancestry of the build they use. Checksum hashes help to check credentials of the issuing source, but arguably these two downloads (app and hash) need to be on separate domains, independent of each other to prove veracity.
That's the first thing.
Second, consumers of opensource stuff, do they bother to check Checksum hashes anyway?
Shame that the downvoter didn't care to share their thoughts with us.
Never mind. Here's my view FWIW:-
Mint's site got hacked a while ago, and dodgy ISO's were being served up.
How does one know what one is getting when downloading anything? If there is a tie-up between Checksum hashes on a separate independent domain - such as distrowatch, then it helps increase one's confidence in what is being downloaded is the real deal.
But Libreoffice is not in the same category as Mint. But one's confidential data is more critical to be secured. How do you safeguard your on-line data when using a gateway such as LibreOffice?
In three words: provenance is key.
> How does one know what one is getting when downloading anything?
You definitely know what you're getting. What you do not know is if that's what you expected to get.
How do you know that when you're logging into the Office whatever site you are really logging into the right site and not a fake one? How do you know that whatever software updates you are getting are really what you're expecting to get (yes I know about signatures)?
The answer is, it depends on the degree of sophistication of both the target and the attacker.
Quite what in God's name this has to do with LibreOffice, or FOSS, or anything else, however, I cannot fathom.
> Opensource [sic] has lots of benefits, but consumers of it have to be savvy about the ancestry [sic] of the build they use.
By ancestry do you mean origin? Or the actual commit history?
And perhaps you would care to explain your actual point? I for one have no idea what you're trying to say.
Spot on.
"......but consumers of it have to be savvy about the ancestry of the build they use. Checksum hashes help to check credentials of the issuing source......"
Whooossshhhhhh...
And that is the sound of what you have said going over 99.999% of consumers heads.
And we wonder why IT is seen as nerdy.
I prefer Google's docs, it's easier to use, no backups or undo history to lose, is free, doesn't need installing of updating does proper collaboration, and above all is very secure (1 document protected by 2FA and revokable permissions, not multiple uncontrollable emailed copies floating about)
For corporate security Google apps for work offers a very compelling featureset.
If only Sony pictures had used this, their hack would have likely not occured, or would have been vastly less widespread
That's fine if you trust Google not to spy on you or do (deniable?) indirect demographics, I don't trust it much, so blacklist its search engine and limited how much I use its stuff, including excluding a lot of data from my Android devices.
You can get a usable Port of LibreOffice for Android i.e. can be used off-line, so is probably harder to snoop on.
Sony had seriously flawed security because corporations eventually regress, because the management isn't exposed to a much risk as an individual or family which fully own a business.
over LibreOffice. Why? Because it seems smother, easier to use than LibreOffice.
Same for me on MacOS. Despite the undoubted technical advances in LibreOffice it's crashed too often for me to be usable. But most worryingly is how the UI seems to be going backward. I'm increasingly thinking of switching to MS Office 2016.
Which they (LO) has done quite aggressively. Even if for no other reason, Apache accepting OpenOffice from Oracle (if Apache had not accepted it, OO would have been shuttered), allowed the relicensing of the entire codebase to ALv2, which was a VERY good thing for LO, since it provided them with true IP provenance and patent protection.
LO could, of course, be "neighborly" and return some patches improvements to AOO, despite not being required to due to their licensing, but have chosen not to, which is their right. But it does seem ironic that LO requires patches to their code to be contributed back, but don't feel the need/desire to do so in cases where it's not required. It proves, to me at least, is that copyleft licenses are all about forcing behavior that one doesn't expect to simply happen, which is a sad outlook.
Outlook™ is sad.
.. but alas the key to the iron grip Microsoft has on end users so they stick with Office 365.
That said, the security problem and bug in Outlook 2016/365 is massive - it polls the root domain of your email address before bothering to access the host you have actually configured, and it takes only a few lines of code to make it give you the account password. It's a good thing only a few know about it (MS claims it's a "feature", but because it is part of auto-config doesn't mean it's actually sane to do this).
To be honest, OO has dropped off my radar quite a while ago. By way of illustration, LO has now matured to such a degree that they have now implemented a sort of "ribbon" clone in the advanced features (it's called Notebook Bar) and to be fair, it is a good clone as it is as ghastly as Microsoft's ribbon and just as productivity destroying. Evidently there was not that much more to add. On the topic of that specific "innovation" - I find it so compatible with the MS ribbon that it is worth avoiding with the same enthusiasm..
At least you have a choice here, though, it's not rammed down people's throat. As a matter of fact, it's hard to find, I just came across it when reading the release notes (yes, I read those, I'm that one hit of last month :) ).
Pen-tester gets past Microsoft VB macro barriers
Outlook Forms aren't macros, after all - but is it a bug or a feature?
It was brought up how bad the licensing chosen when transitioned from Oricle to Apache was announced, it was set up in a way they can not easily include LibreOffice's improvements but LibreOffice can include most anything from OpenOffice other than things like trademarks of OO. Granted one of the reasons for the split was there was a ton of third party improvements that had not been merged into the core code base and they did a lot of clean up too, so it was likely going to be a long time before OpenOffice would be in a position to be doing work that was not already done on LibreOffice even if it had gone well and attracted a much larger set of devs.
Context: I'm a Microsoft Office 2010 user, I never got a click with both OpenOffice and LibreOffice. I do have LibreOffice installed on my FreeBSD powered laptop but that's it. On my desktop it's Word, Excel and all from 2010.
So first of all: a major security flaw? I can see the risks but you honestly need to take this within context as well. It's not as if OpenOffice actively reaches out across the Internet. Also: cause & effect? You conclude that the change was made because of your probing, but can you really be sure of that without having checked what triggered the change?
See, I can do better than you guys here ;)
"OpenOffice is DOOMED, they shown refusal to fix an important flaw in the software. Previously they promised to include one security fix within their next release, but while thinking about writing this message (which took me one week at least, honest! <fingers crossed>) all of a sudden they changed the release notes and removed mentioning of this!"
Sure, I am kidding with the "one week preparations", but if you take that out of the equation doesn't this sound at least somewhat plausible as well? Better yet: it's even hurting the project even more! win win! or.. maybe not.
My stance is simple: just because a project doesn't use the same release cycle as their competitors doesn't mean it's dead. I also couldn't help notice that there wasn't one single link to back up your claims about said security risk. Which leads up to another possibility: there was no risk in the first place and so it got removed. Which is what you noticed, and then drew ridiculous conclusions that it had something to do with yourself.
Tunnel vision much perhaps?
"My stance is simple: just because a project doesn't use the same release cycle as their competitors doesn't mean it's dead. "
I hope you are right. However, having developers on the project mailing list discussing the best way to 'retire' the software is not generally taken as a sign of rude health...
https://arstechnica.com/information-technology/2016/09/openoffice-after-years-of-neglect-could-shut-down/
Not wishing OO ceases but the size and nature of the project makes it difficult for a small group to handle. Also, OO lost too much momentum while Leisure Suit's Minions navel gazed. LO and to a lesser extent MariaDB got a solid jump on their parents during the dithering phase. This hurt OO much more than MySQL.
I have not looked into the licensing issues. I am not sure Apache will modify the license on OO so they could port LO improvements into OO.
Personally I would like a healthy OO as another option against Slurp and I like LO. Having a couple of options also means there is some different ideas about the feature set and UI available.
"Personally I would like a healthy OO as another option against Slurp and I like LO. Having a couple of options also means there is some different ideas about the feature set and UI available."
Yup - LO are refactoring the code base - I remember them saying that earlier in the fork - quite a lot of the code goes back to StarOffice days apparently.
oOo are taking different tack and keeping quite a lot of the legacy code I gather so you have diverging back ends and, as 'lurker' says, a choice of UI models should LO do anything too ribbon like as default.
Note quite Joel Spolsky but it will be interesting to see how the code bases evolve if oOo survives.
Code rot is an obsolescence variant of technical-debt which will bite you later, often as security issues (e.g. in OO probably) or as code which is hard to maintain.
Most code should be written as manageable sized modules for ease of functional testing, and for isolation to allow internal changes which won't break other code as much; it sounds like this is what the LO wisely team is wisely doing with the crufty old OO code, but the obviously Zombie OO project has shufflingly failed to do.
I suppose there was a time when the phrase "fair dinkum" might have occasioned a raised eyebrow anywhere except Australia. When a gf went to study in the UK, she let go with the expression "a coon's age" (meaning "a long time", a decade or more) to collective shock and horror around the lunch table. I'm sure she would have received feedback around a USA lunch table, too.
Because of the market dominance of MS, I suppose that open developers must have spent a lot of time around the lunch table discussing to what extent they should provide a compatibility mode. In other words, they will try to render a document as the document instructs them, but in compatibility mode they would render the document the way a particular version of MS Office would render it. Seems like a no-brainer, but seeking compatibility uber alles is a slippery path.
Around a more exalted table at MS, they must spend a lot of time figuring out ways to get open software to fail to properly render an MS Office document. This also can be a slippery path, though usually a win for the market dominator. E.g. MS-DOS versus DR-DOS.
I use LibreOffice, but not often. In olden days when faced with (the possibility of) screen garbage, I would ask the originator to save the document to a format old even then (was it Word 2.1 ?). That would stand a better chance of indigestion-free consumption by whatever version of AbiWord I happened to be using. That approach is less productive when the document has been published rather than sent.
No point because in the past at least, MS couldn't be bothered to ensure identical page layout between versions of their own products.
Many years ago I had a global publisher of modular educational materials as a customer. When they moved versions of MS Office (or printer hardware) they had to reprint every single page of every single document that was in their current course portfolio because of page formatting anomalies.
Arguably they should have been using software with better markup control in the first place, but I suppose budgets got in the way (an example of short-term gain being a long-term nightmare).
> ...at MS, they must spend a lot of time figuring out ways to get open software to fail to properly render an MS Office document
I don't think they need to. MSOffice makes such a dog's breakfast of layout, font, etc. that it's pretty much a given that well-designed software would struggle with it.
"Free, usable on windows and linux. What't not to like?"
Oh jeeeeez.
Fine, if you are happy for Google to own one more bit of your data. A BIG bit of your data, to go with all your email and all your search data.
I despair. Why do people care so little for their privacy?
To be able to read/write the 365's cloud files directly into the application. You do your stuff locally, and save it out the those other guys "cloud".
This might need to make sure that the formats work correctly, but that is a continuing effort.
At a previous job, I was in a constant tog-of-war with that other software and LibreOffice. They handled tables and indents differently for me, and every time I read back in the saved file it was mushed up. I might have done something wrong (likely), but it did mess things up.
What needs to be done is to persuade a hardware vendor to include it in the "shipped software" by default. I suspect the Redmond people might object though!
One of my clients maintains a daily Foreign Exchange spreadsheet on Excel, and has done for many years. No exotic currencies in there, no exotic formulae or macros or formatting, nothing that a standard four-function calculator couldn't churn out, given time. One day I had a call-out from them as anomalies were creeping into the figures.
It transpired that somehow the spreadsheet had been saved in an Open Document Format supported by Excel, rather than in customary xlsx format, and this, somehow, caused calculations to go awry. Putting it back to saving as .xlsx everything returned to normal.
Moral of story: Even if MS indicate that they support something doesn't necessarily indicate the depth of that support.