European IT Chief Slams Proprietary Software
Neelie Kroes is no lightweight when it comes to open v. closed software. She spent six years as Europe's head trust-buster, and in that time, collected billions from proprietary software makers who sought to corner the market with their closed-source wares. When she spoke, big software — and everybody else — listened.
In February, Ms. Kroes moved on from chasing down monopolists, becoming the European Commissioner for Digital Agenda — the EU's lead regulator of all things information technology. If her recent comments are any indication, she intends to continue her staunch opposition to proprietary software in her new position.
Kroes has never been one to mince words, and she certainly didn't last week while speaking to an Open Forum Europe-sponsored conference. She blasted proprietary software, saying that choosing it over Open Source alternatives can leave nations "unintentionally locked into proprietary technology for decades", and went on to note that even if Open Source options are later implemented, they "risk being systematically ignored."
She told attendees that she intends to promulgate guidelines intended to promote options including Open Source, saying that any government that chooses closed over open should have "clear justification" for doing so. She described the choice between Open Source and proprietary software as being between:
"[T]he one that you can download from the Website and that you can implement without restrictions or the other one which you have to buy which is restricted to certain fields and which requires royalty payments for embedded intellectual property rights -- and the answer is obvious."
She didn't stop there, however. The vendor lock-in that proprietary software causes, she said, is "a waste of public money that most public bodies can no longer afford." By all indications, her time at the Directorate-General for Information Society and Media will be a wild ride, not least for the proprietary manufacturers who have no clue what they're in for.
Image © European Union, 2010
Justin Ryan is a Contributing Editor for Linux Journal.
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
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- 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