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/
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.
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.
No, it's written by Matt Asay ... the Bennett Haselton of tech journalism.
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)
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.
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