Language Selection

English French German Italian Portuguese Spanish

Open office dilemma: vs. LibreOffice

Filed under
OOo is one of the leading competitors to the Microsoft Office suite of business productivity applications. Originally developed as StarOffice in the late 1990s, the suite had been managed in recent years by Sun Microsystems as an open source project. But when Oracle acquired Sun in April 2009, the future of Sun's software offerings -- particularly free ones like -- was called into question. Before long, key developers, unhappy with the status quo under Oracle, began defecting from the project.

The result was LibreOffice, a new fork of the code base that's maintained by a nonprofit organization called the Document Foundation. LibreOffice looks like and it runs like It even reads and writes's OpenDocument file formats. The difference is that LibreOffice is being developed in a fully community-driven way, without oversight from Oracle. (The "libre" in the suite's name is derived from a Latinate root meaning "liberty.")

The question is, which suite should you use? Both and LibreOffice recently announced version 3.3.0 of their respective wares. Both are available as free downloads (although Oracle also sells a version of that includes commercial support). Which one will be the better bet for now or in the foreseeable future? I installed both to find out.

rest here

More in Tux Machines

7 tools for analyzing performance in Linux with bcc/BPF

A new technology has arrived in Linux that can provide sysadmins and developers with a large number of new tools and dashboards for performance analysis and troubleshooting. It's called the enhanced Berkeley Packet Filter (eBPF, or just BPF), although these enhancements weren't developed in Berkeley, they operate on much more than just packets, and they do much more than just filtering. I'll discuss one way to use BPF on the Fedora and Red Hat family of Linux distributions, demonstrating on Fedora 26. BPF can run user-defined sandboxed programs in the kernel to add new custom capabilities instantly. It's like adding superpowers to Linux, on demand. Examples of what you can use it for include: Read more

Why the open source community needs a diverse supply chain

Diversity and inclusivity in the technology industry—and in open source communities more specifically—have received a lot of coverage, both on and elsewhere. One approach to the issue foregrounds arguments about concepts that are more abstract—like human decency, for example. But the "supply chain" metaphor works, too. And it can be an effective argument for championing greater inclusivity in our open organizations, especially when people dismiss arguments based on appeals to abstract concepts. Open organizations require inclusivity, which is a necessary input to get the diversity that reduces the risk in our supply chain. Read more

Red Hat: Kerala, Amazon and More

Programming: Swift, Brilliant Jerks in Engineering, and Career Path for Software Developers

  • Swift code will run on Google's Fuchsia OS
    A few days ago, there was a flash-in-the-pan controversy over Google "forking" Apple's open-source programming language Swift. After a few minutes of speculation over whether Google was going to make its own special flavor of the language for its own purposes, Swift's creator Chris Lattner (who now works at Google) helpfully clarified the situation:
  • Brilliant Jerks in Engineering
    This are numerous articles and opinions on the topic, including Brilliant Jerks Cost More Than They Are Worth, and It's Better to Avoid a Toxic Employee than Hire a Superstar. My colleague Justin Becker is also giving a talk at QConSF 2017 on the topic: Am I a Brilliant Jerk?. It may help to clarify that "brilliant jerk" can mean different things to different people. To illustrate, I'll describe two types of brilliant jerks: the selfless and the selfish, and their behavior in detail. I'll then describe the damage caused by these jerks, and ways to deal with them. The following are fictional characters. These are not two actual engineers, but are collections of related traits to help examine this behavior beyond the simple "no asshole rule." These are engineers who by default act like jerks, not engineers who sometimes act that way.
  • [Older] The missing career path for software developers
    You started hacking on technology thrilled with every stroke of the key, making discoveries with every commit. You went about solving problems, finding new challenges. You were happy for a while, until you hit a plateau. There was a choice to be made. Continue solving the same problems or start managing others. You tried it out, and hated it. Longing to focus on technology, not people, you turned to your open source project. When it became successful, you became an open source maintainer but ended up overwhelmed and burned out. Hoping to get back to doing work that fascinates you, you went work for yourself. Lacking experience running a business, you're crushed with all the decisions you need to make. You’re nearing burnout — again. It feels like you’re on a hamster wheel.