SoylentNews is people
SoylentNews
Over at the Open Source Initiative, Simon Phipps writes about the past, present, and future of Open Source Software as it turns 20 this year. Thought of in a strategy session on how to make Free Software more palatable to certain business interests, the orignal idea was for it to be a stepping stone from proprietary to Free Software by focusing first on the advantages of the developmental model.
Thirty-five years ago when Richard Stallman decided that he could no longer tolerate proprietary software, and started the free software movement, software freedom was misunderstood and dismissed. Twenty years ago a group of free software advocates gathered in California and decided that software freedom needed to be brought to the business world. The result was a marketing program called "open source". That same month, February 1998, the Open Source Initiative (OSI) was founded as a general educational and advocacy organization to raise awareness and adoption for the superiority of an open development process.
Of course, old-timers will remind us that originally software was source and binaries did not count. Up until the late 1970s or early 1980s, when you bought software, it was source.
Source : Happy Anniversary—The Next 20 Years of Open Source Begins Today
Related:
https://perens.com/2017/09/26/on-usage-of-the-phrase-open-source/
(Score: 3, Interesting) by opinionated_science on Sunday February 04 2018, @07:32PM (1 child)
well Ubuntu builds on debian. Of course the amount of money they burnt on Mir, just to have control.
I get why companies want control, it's their money.
But the world would be a much better place if API's and specs were written first, to avoid the proprietary mould from infrecting GPL principles.
Make no mistake, EVERY $CORP wants TOTAL control. Software and remote operation just makes it easier.
GPL forever.
11 years Windoze free....
(Score: 2) by Grishnakh on Sunday February 04 2018, @08:28PM
I get why companies want control, it's their money.
Companies want control because they can make more profit that way. Lock-in gets you more profit because customers can't easily leave for a competitor, for instance.
But the world would be a much better place if API's and specs were written first, to avoid the proprietary mould from infrecting GPL principles.
If your software is GPL and freely downloadable, having APIs written beforehand isn't all that necessary since you can just consult the source for how the APIs are now. Of course, if the devs are constantly changing the APIs a la Gnome3/Gtk, that can be a real problem unless you fork it, but that doesn't usually work out well unless you can get everyone to follow your fork (like with XFree86->X.org).
GPL forever.
GPL is great and all, but what if you're a company and you need some piece of application software for important business reasons, and your only real choices are proprietary? Best case, that proprietary software should run on Linux, so you can at least have a FOSS IT infrastructure and not have to worry about Microsoft screwing everything up with one of their updates, and so that you have your own control over it, even if you don't have control over every single application you run on it. To me, it's FAR more important for the infrastructure to be FOSS than for applications to be. Proprietary file formats are of course a problem, but not nearly as bad as your whole OS being proprietary. If I were more clever, I'd make some kind of analogy here about building foundations.