/etc/rant - Skim Cream not Scum
When did Microsoft lose its status among open-source developers as the evil, or better still, incompetent empire? When did open-source developers stop trying to make software better than Microsoft's and start imitating everything Microsoft does? Why do we have to have an open-source Outlook, or an open-source dotNet? Sure, there are examples of how we do things better in Linux than Windows. But I'm getting really tired of the monkey see Microsoft, monkey do Microsoft mentality that has infected open source. And the operative word here is “monkey”--hint, hint.
Aside from being open and free, isn't superiority what got Linux where it is today? Once upon a time, Microsoft was under intense pressure to catch up to Linux stability (in my unhumble opinion, Microsoft still has a long way to go). Now we have several projects that exist for no other reason than to to catch up to and duplicate Microsoft software. Worse, we're duplicating architectural nightmares like the registry, and with no other apparent purpose than to be more like Windows.
I have nothing against cream-skimming the best features of Windows for use in Linux. But creating a registry for Linux is not cream-skimming. It's pond-scum-skimming. What happened to the days when people were appalled at the idea that you'd have to edit a registry in order to make this or that feature work the way you wanted? I don't care if the registry is binary or XML. It's a maintenance nightmare.
Next time you visit Redmond, take a look at big hole with teeth marks in the Microsoft butt. That's a “came back and bit it” bite mark left by the registry. While Microsoft is trying to get around its mistakes, we're busy duplicating them.
Here's another example. Emulating what OLE 2.0 brought to Microsoft Office is not cream-skimming. It's biohazardous-medical-waste-skimming.
I remember the original Microsoft demos of OLE 2.0. You paste spreadsheet cells into a Word document. You click on the cells and the word processor magically transforms into a spreadsheet program. That makes good demo, but did anyone ask what real value it offers? Aside from looking cool, that is? This feature is bad not because of what it does, but because of what it fails to do. It fails to make it easy to create a live link between the original spreadsheet data and what you paste into the document.
Fortunately, not everyone has imbibed from the punch bowl of Microsoft cool-aid. EIOffice, although it looks and feels more like Microsoft Office than OpenOffice.org or KOffice, actually came up with a fresh idea. Imagine that. Innovation. But it took a commercial company, not an Open Source community, to do it. The folks at Evermore Software (the makers of EIOffice) must have at least one non-Microsoft drone on board to enlighten the developers as to what really matters. EIOffice gives you a menu selection to paste a bit of spreadsheet into a document where the cells are live-linked to the original spreadsheet data.
And this next bit of information should send open-source fanatics into a tizzy. EIOffice is based on that evil, despicable language called Java. How dare they? Mono C#, Python, Ruby, maybe even Perl. But Java? Won't that encourage Sun to become dictator of the world if EIOffice gets popular? It's perfectly fine to copy Win32 DLLs in order to make Linux do Windows tasks, but heaven forbid Linux should be infected with a Java runtime. How Sun replaced Microsoft as the evil empire is beyond me. But don't get me started on that.
Back to OLE 2.0 and its successors. Of course, the OpenOffice.org and KOffice folks have faithfully duplicated this monstrosity. Hey, it's how Microsoft Office works. It must be the way to go, right?
That's what they want you to think. Who is they? I don't know, but I can't help but wonder if one or more people within some of these open-source projects are Microsoft moles.
“Here's the plan. Infiltrate the Open Source community and neutralize it. Convince them that the only way to compete with Microsoft is to create open-source versions of Microsoft's great software and development tools. Without our patents, you'll always be several steps behind everything we do. And the fact that you're imitating us makes us look like the clear innovation leaders. End result? Free advertising and marginalization of the value of having Linux.”
It's time to boot the Microsoft suck-ups out of the Open Source community. Give them a free copy of Windows XP, Visual Studio dotNet and two months to use these to create a navigation system for the rocket we'll use to send them to Mars.
Yeah, but what do I really think?
Nicholas Petreley is Editor in Chief of Linux Journal and a former programmer, teacher, analyst and consultant who has been working with and writing about Linux for more than ten years.
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SourceClear Open
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
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