Open Source In the Datacenter: It Was Never About Innovation
An anonymous reader writes "The secret to open source innovation, and the reason for its triumphal success, has nothing to do with the desire to innovate. It's because of the four freedoms and the level playing field (and agility) that was the end result. It's like Douglas Adams' definition of flying: you don't try to fly, you throw yourself at the ground and miss. This article explains why it was never about innovation — it was always about freedom. Quoting: 'When the forces of economics put constant downward price pressure on software, developers look for other ways to derive income. Given the choice between simply submitting to economic forces and releasing no-cost software in proprietary form, developers found open source models to be a much better deal. Some of us didn't necessarily like the mechanics of those models, which included dual licensing and using copyleft as a means of collecting ransom, but it was a model in which developers could thrive.'"
Open sores in the datacenter? So that's how the NSA got its backdoors into Google and Yahoo?
Groog the Closed-Source Troglodyte says:
DATACENTERS ARE COMMUNIST
90% of everything is crap, but at least with open source you can find out why instead of waiting for the developers who can't reproduce your problem.
This is just an opinion piece, not even remotely news.
Could someone explain how CopyLeft ransom works?
Why pay when you can have it fo free?
did you forget to take your meds?
Its about kicking MS ass, man!
My way! Your way uses the wrong libraries and language.
choice? what do you mean? my way is clearly the only best way.
When people say Innovative, we think of something that when we see it, we go Wow this is so cool I would never think of of that myself, and usually throws the rest of the industry in catch up mode.
Now the iPhone (not the iPad) was an innovative idea. Phones before the iPhone had external keyboards, at the expense of of screen size, or thickness. The idea of very few real buttons at the time was very foreign to us. And using gestures seemed almost impossible, as many early gesture systems had a lot of complicated gestures to get tasks done.
The iPhone wasn't innovative based on its features, there were other companies that had phones with more features or better hardware. But the innovation was able to successfully make a phone, that the advance feature were accessible and to the end users. The idea of say browsing the web on your phone, or have it as your main method to check for email seemed silly before, today it is quite common.
What happened after the iPhone kicked off, it threw the Industry in catch up mode. It took years for good Android phones to get into the market to start competing, and these new phones all are based on the iPhone.
Now the iPad isn't that innovative, it was easy to realize you take your iPhone and just give it a bigger screen, and fit better processing.
Other innovative products.
ID software 3D shooter. Wolfinstine 3d and Doom. They had some wire-frame attempts, and a few polygon based games. But games before that for the most part where 2d sprite based (Side Platform like Mario, or top down like Zelda), specificity for fast paced action games.
Nintendo Entertainment System. Unlike the Atari and other predecessors it didn't give any allusion that it was a person computer, just a straight game console. Priced more affordable than the others, and focusing on games.
Innovation is very rare. Most of the time it is copying someone else idea and tweaking it so there are different set of trade offs. Now their tweaks may change the market, but not as much as a innovative product.
How you choose to license your product, isn't really that big of a deal. Open Source, sure people can tinker with it coming with some new ideas. Commercial Software will have paid employees trying to come up with something new.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
When I write code for personal reasons, I always release it under the Affero GPL v3+.
It saves me the time and effort of attempting to monetize or control every little snippet of code that I write just for fun or just to learn something.
It also ensures that nobody can commercially exploit the code without A) paying me for a non-GPL license, or B) contributing back to the community.
As a side effect, it makes a great way to show off my coding skills to potential employers.
They can look me up on GitHub and evaluate my code and skills, but they still have to pay to play.
I'm not a libre software zealot. I don't believe that everyone is under a moral obligation to release their source code.
However, I do find the Affero GPL effective at protecting my non-commercial interests and providing an assist on my commercial interests.
That is why I use the license, and encourage other software developers to do the same.
Seems like a lot of open source stories lately are coming from highly questionable, if not zealot types of sources.
Let's cover two points before ya'll mark this as troll or flamebait.
GNU is the lesser evil:
A program is free software if the program's users have the four essential freedoms:
The freedom to run the program, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
There's no "closed source is evil, propietary software is designed by money grubbing capitalists, all software wants to be pirated" point of view.
Richard Stallman himself however does have an "evil" agenda if you will. (from wikipedia)
Stallman pioneered the concept of copyleft, which uses the principles of copyright law to preserve the right to use, modify and distribute free software, and is the main author of free software licenses which describe those terms, most notably the GNU General Public License (GPL), the most widely used free software license.
The GPL violates all four points in that:
1. The GPL prohibits commercial use or sale of software without releasing the source code "somewhere else for free so I never have to buy it"
2. The GPL has viral components to it that, even if you make changes to it, someone who wants to benefit from that change must accept the GPL or not use the change, even if they are simply studying the code. So this means that if you want to develop something that works like or with the the GPL software, you can never study the GPL software without making your software GPL too.
3. The GPL makes it impossible to charge money for any part of software, be it source code, art assets, music, sound, or video. Every part of a "GPL" program must be redistributed without fee, so even someone who mis-appropriates something from the public domain can "GPL it" and and render the PD invalid.
4. Nobody benefits from software that they have a license-gun to their head.
Nobody should be using any GPL software, less what you make become GPL too. If you're fine with that, then maybe the GPL is for you, but for the vast majority of people who just do not want to deal with political footballs, the GPL is quite evil. People who wish to make games in particular and not have their game pirated, ransacked by chinese gold botters, and utterly destroyed two days out of beta can not use any GPL software whatsoever, because access to the source code means someone just adds a "letmecheat=1" to the source code and your game is ruined.
There are some really good reasons to have things like GPL operating systems,GPL compilers and GPL drivers, because these are the parts that make a computer something more than a blackbox. Past that point, mandating that everything compiled with GPL compilers that runs on the GPL OS must be GPL licensed and free is folly.
Copyleft ransom ( http://en.wikipedia.org/wiki/Threshold_pledge_system )
Is the act of giving copyrighted works away for free, but not producing it in the first place unless a set threshold of money is given. Basically what everyone is doing with Kickstarters today.
There is nothing wrong with this.
The bit about developers using "copyleft as a means of collecting ransom,".
This doesn't sound like a complaint from the end user (data center) for all the nice, free software. It sounds like butthurt from proprietary s/w vendors who can't find a way to take open code back into a closed product.
Have gnu, will travel.
One thing I don't get - if there is a downward pressure on prices on developers, how does adapting an Open Source model help them? It's not like they get extra money for it if they reveal their source code.
Also, the 'four freedoms' have never been about making better software, as RMS never tires of pointing out (and it shows). They've been an end in itself. If you write a software - no matter how bad, but simply put it under a A/L/GPL license, RMS would be pleased. Your software respects the 'freedom' of your neighbors, who you must help, as per Freedom 2.
But I doubt that the desire to put Open Source in the datacenter had anything to do with any 'freedom'. It was about putting better software out there. Since the existing datacenter hardware was tied to the support contracts that a Microsoft or Sun/Oracle or HP would provide, moving to FOSS meant that any datacenter that adapted it would determine its own support timelines, since the open source meant that they could hire their own developers to maintain it beyond upstream support, and also, the upstream projects had no strong reason to EOL a version, unlike commercial entities.
The innovation part - this part is not completely true about FOSS, since there ain't millions of programmers interested in the project, and so the software usually doesn't get examined except by its developers, and maybe some very interested customers. Where FOSS helps is that if a customer has esoteric hardware, the software can usually be ported to it to exact the maximum life out of the system, as well as provide a uniform software platform for heterogenous computing environments.
Some of your premise is correct - charging for "copyrighted works" is perfectly fine, and even supported by the idea of Open Source. But, your GPL Violations list and general dis'ing of GPL is BS, IMO.
1. GPL does not prohibit commercial use of software. GPL simply states "respect the applicable licenses".
2. Making use of a GPL library does NOT automatically make my code assume a GPL license. If I use libraryX that is GPL'd, then yes, I need to respect the license for that library and ensure I include the source code for that library with my package. Any changes I may feel I need to make to that library fall under the license for the library and needs to be included in the source code. However, the rest of MY code get's whatever license I want to give it - I just can't override the license for the library itself.
3. Given point 2, then your point three is utterly wrong. If I can set the license for my app as I choose, while respecting the licenses of any sub-systems I may use, I can still charge what I want for my app.
4. Apply your point 4 to Microsoft. After all, you can't say they don't keep the license gun to your head and they clearly benefit nicely. But then apply the same to Red Hat, who is a billion dollar company built using GPL based software. Nobody benefits - yeah right.
You need to understand the licensing quagmire better rather than just spewing out someone else's story. Yes, that is someone else's story - I've heard this one too many times over the past 20 years and every instance has proven to be crappy propaganda put out by those whose bottom line is threatened by Open Source and Free software.
What really happened was that new ways were found to monetize open source. Most of them involve advertising. Some of them involve spyware. Others involve making programs dependent on "the cloud", or on an endless stream of patches, so some company can cut off your air supply unless you pay.
I don't see why he's contrasting things that, instead, worked together with synergy. Strikes me as a really short-sighted way to approach the success of Open Source software.
$.02, etc.
-Slarty
The idea of open source is good - take a product that is useful to you and have the ability to modify it as you see fit. Or contribute to an open source product with like minded people for the benefit of the whole. In reality though, open source is destructive to innovation because of "the fine print". Programming is now less about writing good and innovative code than it is about the licensing. Companies have to find ways around this licensing in order to use the open source code in order to churn out a product that they can use to make a profit. When a software company can't make money selling software - they don't last long. After observing this model in action over the past years, open source is destructive to the laws of nature that drive innovative people to found companies based on a product that would otherwise thrive based on simple supply and demand. Finally, open software and "free software" is most destructive to good software engineers themselves. What a foolish thing to do - to take your talent and assign it a NULL value. Being able to write good software is a gift that few people possess. We should be paid well to do it, but instead we are handing the ability to make money over to lawyers and sales crews. Engineering is now a group of replaceable cogs. If you're truly talented, you're wasting your time in this field. Make software proprietary and of great value. Then we'd start to see gifted and talented people making an effort to use their talents in STEM careers.
It was about paying as little as possible. Given the choice between licensing something for tens or hundreds of thousands of dollars or paying nothing, most people will opt to pay nothing.
Not everything in the cloud is open or free. Amazon Web Services are proprietary and metered, for example, and lots of people still use them. Why is that?
I think it's because AWS decided to support two of the four freedoms, and those are the important ones. Basically, give people tools, and let them build what they want with them, without having to ask anyone for permission.
"We receive as friendly that which agrees with, we resist with dislike that which opposes us" - Faraday
2. Making use of a GPL library does NOT automatically make my code assume a GPL license.
Where the hell does this bullshit keep coming from? The license isn't that fucking hard to read.
Here's a direct quote from the motherfucking license:
The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language.
Thus, if your program contains any GPL code whatsoever, it is considered to be a derivative work by the GPL.
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, if you use any GPL code at all, the GPL considers your program to be a derivative work, and demands that it assume the GPL license.
Granted, the license doesn't make this as clear as it could, but there's not a whole lot of debate about it. Just go ask the glibc people what they think about you compiling a program with -static and then not releasing the source code.
This is what people are talking about when they complain about the GPL being a viral license. There's no reason I shouldn't be able to take my BSD licensed program and copy one GPL licensed file into the source tree and keep the BSD licensed code under the BSD license and the GPL licensed code under the GPL license. However, I can't do that, because the GPL demands that the entire project become GPL licensed. It's bullshit because it only results in code that was previously available under a more liberal license having more restrictions added to it.
n.T. /. support umlauts? öüä
BTW: Does
* Freedom to change shitty design decisions by the author(s). *cough*GIMP*cough*
Anons need not reply. Questions end with a question mark.
Capitalism requires innovation, for added-value or decreased cost, to increase profits.
Increased cost increasing profit is exploitation externalization for a corporate-welfare economy/state [IOW: Screw the consumer].
The present un-American economic model of US is flawed and crippling our progeny, failing posterity, and externalizing US providence.
Unaccountable leaders are masters, and unrepresented people are slaves. How do US and EU fare?