Why the Office Format Wars are Not Over
Gone are the days when free software could blithely ignore what was happening in the world of proprietary code. The two approaches are now inextricably intertwined as more and more users and companies choose to run both. One paradoxical consequence of this is that as free software becomes more widely deployed, Microsoft's impact on it becomes greater. Against this background, a recent shift in Microsoft's public statements about open source assumes a particular importance.
Although you still come across the odd veiled threat against open source, the general approach seems now to be more conciliatory. Perhaps the clearest manifestation of this new policy of cohabitation is the creation of Microsoft's Open Source Software lab under Bill Hilf, and the CodePlex open source repository.
Another example of the gentler, kinder Microsoft came from Brian Jones in the context of office file formats:
I think at this point we can really move onto more productive and collaborative discussion and admit that we are no longer in any sort of "file format war." If we ever were really in a war, it's now over, and both sides are winners.
At first sight, this statement is good news for the OpenDocument Format (ODF) standard and open source. It suggests that Microsoft is no longer out to crush this upstart that threatens the hegemony of Microsoft Office, one of the main pillars of the company's income, but is content to live and let live. However, statements elsewhere – by none other than Bill Hilf – put a slightly different perspective on things:
Open XML and the OpenDocument Format (ODF) must be allowed to compete in the market, where adoption is not determined by a vendor or standards body, says a Microsoft official.
Bill Hilf, general manager for platform strategy at Microsoft, said the market should decide what the prevailing standard should be in the war between the company's Open XML (extensible markup language) document format and the ODF.
"It's like VHS versus Betamax, where the market selected the one it wanted based on values"
This sheds an interesting light on Jones's statement that “both sides are winners
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!
- Stunnel Security for Oracle
- SourceClear Open
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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