The New Struggles Facing Open Source
An anonymous reader writes in with this story about the open source movement's contentious beginnings and the points of trouble it faces today. "The early days of open source were fraught with religious animosities we feared would tear apart the movement: free software fundamentalists haggling with open source pragmatists over how many Apache licenses would fit on the head of a pin. But once commercial interests moved in to plunder for profit, the challenges faced by open source pivoted toward issues of control. While those fractious battles are largely over, giving way to an era of relative peace, this seeming tranquility may prove more dangerous to the open source movement than squabbling ever did. Indeed, underneath this superficial calm, plenty of tensions simmer. Some are the legacy of the past decade of open source warfare. Others, however, break new ground and arguably threaten open source far more than the GPL-vs.-Apache battle ever did."
The cloud... GCE, AWS/EC2 etc.. that are the biggest threat to Open Source. Things like S3 with its proprietary protocol, developers falling in line for RDS and Dynamo. In short, locking yourself into very expensive, closed alternatives because: "It's easy". The battles never went away, they have just shifted. If you are paying attention and not spending all your time reading CTO magazine, you can see this.
Get your PostgreSQL here: http://www.commandprompt.com/
Open Source pushovers getting walked all over by corporations finally starting to realize that maybe freedom is sort of important
The struggle now is how to keep people from destroying things. FireFox is a disaster. Gnome is useless. Seems like people take over these projects and tear them to pieces.
It was the best of times. It was the worst of times. All I know is gimmee mines!
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
What people don't realize is how systemd is a big battlefield. This is a program that wasn't placed into userspace as close to the kernel as possible just because it was better than init, sysv, GRUB, and the many utilities that it replaces... but was dropped into place for pure political reasons.
This only has damaged OSS's reputation because of the incompatibilities with systemd and previous applications that worked fine starting from /etc/rc.d, but adds major security threats, since systemd is this monolithic program that has the ability to listen and take commands via the network... with no real auditing and code vetting to ensure that this doesn't result in a massive remote root issue.
So, staying that flamewars in OSS are dead is wrong... systemd is the biggest schism in the UNIX world since AT&T and BSD parted ways... and unlike the licensing issues of the two distributions, systemd and shoving it down people's throats appears to an outside observer to be mainly about ego, not adding reliability or security.
Wait, are we talking about new problems that are now having to stand up to open source? Or are we talking about open source having new problems with which it has to deal?
the argumentative logic for BSD vs GPL is what i suppose TFA is batting around, and yes its still a very real argument for many. BSD being the license many concede is for a perfect world, but GPL being the only stick with which to ostensibly beat the far-too-often occurance of a corporation with its hand too far in the cookie jar. those kinds of arguments will never change, and in many ways they help define our character and shape our resolution as projects.
So lets tackle the argument, which is basically "openstack is a crazy project full of argument." Openstack is a hodgepodge of various contributors because it works, its an escape from the traditional hegemony of vmware and storage vendors, and those same vmware and mass storage vendors are clawing tooth and nail into the project to at least be part of it, as opposed to die quietly as theyre being instructed to do after having their software as a license cashcow model sidestepped entirely. Samsung and netapp are pushing blobs upstream, diligent open source project managers are kicking them back, and the cycle begins anew each time. The pedantic argument that open source is free to use but not free to build is one we've heard countless times, but plenty of non-corporate sponsored projects exist because hackers want them. Clemens Fruhwirth in 2004 created LUKS, Roy Marples wrote OpenRC, and Timo Sirainen wrote Dovecot and IRSSI because hackers wanted them and so did he. Corporations will always throw resources at software they use, the difference today is that softwares intrinsic value as open source is finally being realized.
Good people go to bed earlier.
No, it's written by Matt Asay ... the Bennett Haselton of tech journalism.
With the near Jonestown-like acceptance of systemd (controlled by one dominant company with lucrative NSA contracts, if not even deeper ties), the fait is pretty much accompli.
Much like the US itself, all we can hope for is a somewhat benevolent dictatorship in everything but name.
I should have closed the tab when it opened on an infoworld story.
Services to support Free software has proven to be a viable business model. IMO, that's a huge win. But, VCs aren't going to get too many IPOs out of that and infoworld probably has some newer advertisers thanks to Free software, but nothing like a Google or Microsoft.
The only threats on the horizon are continued support of increasingly draconian intellectual property laws. They impact everything, not just for software. Two examples: economic growth is constrained and the expansionn of basic human knowledge is restricted. It's returning to a feudal society structure. THAT, in my opinion, is the actual threat.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
Seeing cororate interest in Open Source / Free Software grow bigger, I am slowly moving towards the camp of the Idealists, like RMS.
Just looking at Linux, the kernel. It's great that it is being used in Android, and that it has a billion users there. But Android is not free in the practical sense for the enduser. They can never update their device to a newer version, because the hardwaredrivers are tied to the kernelversion. "Just buy a new device", Google and the manufacturers say. Just what GNU was all about in the beginning, "just buy a new printer".
Similar corporate interests are happening at Red Hat, which is pulling all the sheets in their direction. Their ideal is to have every Linux distro be similar, like RH. And we are "happy" to just take their software and use it, because it is so pragmatic.
The good thing about Free Software is, you can always fork it. But the barrier to do so is quite high, so there needs to be a lot of frustration for that to happen.
We will see what will happen to GNOME3, Mate and Cinnamon. I wish the later 2 projects the best.
Well, don't worry about that. We can get you back before you leave. (Dr. Who)
FTFA with my bodface: "The early days of open source were fraught with religious animosities we feared would tear apart the movement: free software fundamentalists haggling with open source pragmatists over how many Apache licenses would fit on the head of a pin. "
Is this what it has come down to? Really?
The rest of the paragraph is hyperbolic nonsense.
Skimming over this article, I see a lot of buzz words thrown about and very little content of interest.
Bored now.
AGPLv3 solves exactly this problem.
The question of open source is really -- do you have a secure upgrade path. If Windows goes away, and software you use depends on their software, you do not. If you use software based on a BSD/Apache2 license, and someone extends it and makes the result non-open source, and the software you use begins to require these extensions, you don't have a secure upgrade path anymore. GPL solves this problem and guarantees that you will always have an upgrade path, because derivatives need to be open source.
I think this is really the key point, and why purism in software licensing should not be laughed at by "pragmatists". Like for example distributions that do not include closed source software (Flash) or drivers (nvidia), because "pragmatists" want it to "just work". If you go down that path, you are making yourself dependent on a company going the path you want. You get into a situation 5 years down the line where even more software depends on closed source (e.g. mono/.NET), and it is out of your control. That's why I think purism in open source software is still relevant.
Pragmatically speaking, the upgrade path of open source software packages is not in your hands, but in those who are experts in that package's code, and those who invest time in it. The point is rather that if you get annoyed enough to pay someone, you would be able to get control back, while with closed-source extended BSD/Apache2 packages, you would not. You would need to re-invent that software.
For Web services, I think it depends. If the company provides proprietary data, then it doesn't really matter whether the software to access it, or the API is open source. You will have that dependency, until you have open data.
In summary, I think one should ask oneself: In 5 years, when this platform is outdated, and the company goes away or refocuses, what will I do, and am I prepared for that. Who am I dependent on? Having a community of millions of programmers which are in the same situation helps, because only one has to solve the problem and open-source it for an upgrade path.
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
But once commercial interests moved in to plunder for profit,
What a stupid, dogmatic thing to say.
Let the buzzword hoppers be the pioneers who get arrows in their backs before the hard lessons of "The Cloud" are learned and publicized.
In my opinion we need better standards of file and data representation, and stack versioning for the cloud to work effectively. Vendors would have to cooperate to pull it off, and that's often the hard part.
For clouds to fulfill the virtualization role they claim to provide, it has to be just as easy to leave (migrate) a cloud as it does to join. Vendors typically make joining easy but leaving hard to order to hook you and keep you hooked. (Cue Eagle's "Hotel California")
Table-ized A.I.
Money talks. There are great financial incentives to destroy competition that exists freely. The only possible weapon to fight that is publicity.
BSD and Apache are both Free licenses. This author is not well informed.
.... 'what if' NFL mock drafts.
From the article, at the bottom.
Matt Asay
A longtime InfoWorld contributor and former intellectual property lawyer, Matt Asay is currently VP of Mobile at Adobe. The views expressed are his own and not that of his employer.
A lawyer working for Adobe?
The greatest problem for Open Source is proprietary corporations. And people who only look at the bottom-line
This license allows anything, except any kind of lawyer profit and change this license.
You realize that open source software isn't the same thing as libre software right? Oh you don't, then why don't you let the adults converse.
Could you explain the difference? The Debian Free Software Guidelines and the Open Source Initiative's Open Source Definition are almost word for word the same.
Now I have to explain to potential clients why the software I'm selling isn't free. The simple explanation is 'because I like to fuking eat', 'because I have to pay rent on my office', 'because I have to pay my ISP'.
OSS: don't do me anymore fuckin' favours.
What people don't realize is how systemd is a big battlefield. This is a program that wasn't placed into userspace as close to the kernel as possible just because it was better than init, sysv, GRUB, and the many utilities that it replaces... but was dropped into place for pure political reasons.
Yeah, I really don't know if that's right or wrong or what. I know I don't like it either. For me, multiple features of the UNIX design ideas that has made Linux successful are being openly violated, practically with contempt. Per the wikipedia page on the UNIX philosophy: the power of a system comes more from the relationships among programs than from the programs themselves.
Systemd directly harms the server admins like me. I don't understand the urgent need to have the init system minding other daemon's business. It's not that there's no precedence for it, but, init doesn't need to check time, be involved in my bluetooth stack, xorg stack, etc. other than starting it, polling it, and stopping it.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
I remember open source being committed projects done by a community of volunteers. Not big corporation like Canonical or Red Hat or even Google. All of which have taken open source to a new level of success but on the backs of diminishing its value as open source. When I see projects like Mozilla basically take open source to a new level but then allow what got them there to degrade to a point that you wonder if they lost their way? I say the same about Ubuntu and Red Hat and
others. Who seem to see open source as a way to get a cheap path towards a good OS that eventually becomes a commercial and proprietary like product.
Yea, you can say Chromium and Chromium OS are still open source. But they definitely benefit only from Google Chrome and Chrome OS. We still see some real
true to open source projects and they still offer truly community involvement. At least until some corporate giant see's it as their success story.
Pretty much: Yes.
What Hans Reiser did to his wife Nina was pretty sexist. Even if you espouse relatively less fatal versions of his views, you should probably be banned.
'Tonight Brad Smith, general counsel for Microsoft, delivered the “footnote” address at the Open Source Business Conference 2008. I asked Brad to speak because I figured it was the shortest path to getting clarity from Microsoft vis-a-vis open source and the nettlesome legal issues that have plagued Microsoft’s relationship with open source' ref.
"I understand that Microsoft may be using the OSI's license approval process to its own ends, and potentially ends that may be anti-open source. I'm still not sure, however, that it's appropriate to treat an incoming license from Microsoft any differently than one that comes from Linus Torvalds ref"
Hans Reiser did nothing wrong. He followed the law in Deuteronomy, which was the correct thing to do.
People like you should be killed.
Well said! I wish he would stop writing tripe, he's completely out of touch when it comes to anything free software or open source.
Anonymous Troll: "The struggle now is how to keep people from destroying things. FireFox is a disaster. Gnome is useless. Seems like people take over these projects and tear them to pieces."
'Pale Moon is an Open Source, Firefox-based web browser available for Microsoft Windows, Android and Linux (with other operating systems in development), focusing on efficiency and ease of use. Make sure to get the most out of your browser!'
All the arguments against systemd are bogus. Even the things it claims to fix it does not. The strategy is a pure PR strategy one: Promise the holy grail, claim is fixes some things that are actual minor problems, and make sure to get people on-board before you actually deliver. Then make it very, very hard for them to leave again, and you never have to deliver. (They cannot deliver on most of their promises anyways, in part because it is impossible and in part because they are incompetent.)
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
I think ultimately the answer will be Hurd, Stallman and co will keep it ideologically pure and eventually it'll get bigger as more people abandon corporate Linux.
The recent http://xkcd.com/1508/ shows human civilization ending in around 2042. There's a pause afterwards with no OSes run, and then in 2059, GNU/Hurd.
I remember sigs. Oh, a simpler time!