Miguel de Icaza plays fast and loose with the facts and history
Miguel de Icaza, in this weblog entry says, "Facts barely matter when they get in the way of a good smear. The comments over at Groklaw are interesting, in that they explore new levels of ignorance." This comment rings especially true of his weblog entry. For example, Miguel states...
We have been working on OpenOffice.Org for longer than anyone else has. We were some of the earliest contributors to OpenOffice, and we are the largest external contributor to actual code to OpenOffice than anyone else.
Say what? Who created OpenOffice? Who bought it? Who opened it? Anyone ever hear of Star Division gmbh or Sun? Since when did Novell become the earliest contributor to OpenOffice.org? The earliest and largest external corporate contributor, maybe. I'd like to see some hard facts to back up an assertion like that (not that facts matter, as Miguel admitted), but his hyperbolic boasting of Novell's contribution is obviously overblown. And is a contribution that doesn't make it into the main code base really a contribution? After all, in the same blog entry, Miguel himself makes much of the fact that Novell's OpenOffice.org really isn't THE OpenOffice.org. It's Novell's unique version, patched and modified.
And of course, the code that we write to interop with Office XML is covered by the Microsoft Open Specification Promise (Update: this is a public patent agreement, this has nothing to do with the Microsoft/Novell agreement, and is available to anyone; If you still want to email me, read the previous link, and read it twice before hitting the send button).
I agree. Read that link twice or even several times, and then blast Miguel with an email. First, the fork isn't just about Office XML. It's about things like Excel VBA, which is not covered by the above Microsoft promise. Indeed, here is the only relevant technology covered by that promise:
Office 2003 XML Reference Schemas
Office Open XML 1.0 proposed Ecma standard
So the promise, worded in such twisted language that even a lawyer might not be able to decipher it, covers an old standard and a proposed standard. And this is supposed to reassure us, how?
Sorry, Miguel, but you seem to have been on an ongoing crusade to inject as much of what Microsoft produces into Linux, from Mono to Evolution and now things like Excel VBA. You say it is all in the name of providing interoperability, but at what cost? Add to that the exclusive patent agreement, and the once absurd notion that you're a Microsoft mole with a mission to infect Linux with IP that promotes Microsoft starts to become plausible. Not conclusive by any means, but plausible.
Regardless, I stand on my call for OpenOffice.org and other FOSS project leaders to refuse to adopt any contributions from Novell into the mainstream code base. Let Novell offer all the patches it wants, but keep them out of the projects. Let Novell fork OpenOffice.org if it wants. That's fine. Meanwhile, I urge contributors to the main branch to work on interoperability that does not include Microsoft patents, but includes means of translating things like VBA code into something native - and GPL - to OpenOffice.org.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Control Your Linux Desktop with D-Bus
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Returning Values from Bash Functions
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide