Linux: You Get What You Paid For (When You Bought Windows)
If you've been an Open Source advocate for any significant amount of time, you've no doubt heard someone say, with a sneer in their voice, "You get what you pay for". Let it be noted, I really hate that cliche. It does make me think, however, about what you really get when you purchase the license to use a commercial operating system like Windows or OSX. Here are some things the operating systems themselves offer for the money:
What Windows & OSX Provide
- Consistent interface
- Standard API interfaces
- System updates, at least for a significant amount of time
- Rudimentary applications (Safari, IE, Wordpad, Textedit)
- Tech support (often additional cost though)
There are many other "features" that get attributed to Windows and OSX, but I don't think it's fair they get all the credit. Sure, there are more drivers and more commercial software available -- but that's really the doing of vendors, not the OS manufacturers. With the advent of Vista and its hornet's nest of problems, really the only thing Microsoft has going for them is market share. And cash.
What happens when hardware vendors start installing OEM versions of Linux on more hardware? It's already begun, and although it's happening slowly, it is happening. Think about the advantages OEM vendors have when they choose Linux:
Linux Advantages for OEMs
- I assumed it was obvious Linux offers everything from the above list, but there was confusion, so please note that I do understand Linux offers everything listed above. Except maybe a consistent interface, but that's another article altogether
- Free, enterprise grade software bundles
- No need for bundled crapware trial software to offset licensing costs of the OS
- Virus & Spyware resistance.
- Compiz? :)
There are some issues regarding the installation of proprietary codecs, Flash, MP3 support, etc -- but I'm sure that could be easily scripted into the initial setup process. I know that installing a fully functional Linux OS is no longer difficult.
I'm excited about the future of Linux. Yes, the competition has mountains of cash. Yes, they have an astronomical installed user base. Yes they work hard to protect their interests in proprietary hardware support. But we're patient. We're smart. We have nothing to lose, and what we do have, we're giving away.
It's a good time to be a Linux user.
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
|Trying to Tame the Tablet||May 08, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Home, My Backup Data Center
- Tech Tip: Really Simple HTTP Server with Python
- Please correct the URL for Salt Stack's web site
1 hour 1 min ago
- Android is Linux -- why no better inter-operation
3 hours 17 min ago
- Connecting Android device to desktop Linux via USB
3 hours 45 min ago
- Find new cell phone and tablet pc
4 hours 43 min ago
6 hours 12 min ago
- Automatically updating Guest Additions
7 hours 21 min ago
- I like your topic on android
8 hours 7 min ago
- Reply to comment | Linux Journal
8 hours 28 min ago
- This is the easiest tutorial
14 hours 43 min ago
- Ahh, the Koolaid.
20 hours 21 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?