Locked-Down Tablets Endanger FLOSS For End Users
itwbennett writes "If you buy into the idea that tablets (and ultrabooks, and smartphones) in the enterprise are nothing more than glorified thin clients, then Microsoft's Surface presentation seemed more flashback than future. And if you're a fan of free software, the announcement might also have struck fear in your heart. While Microsoft has never locked out apps based on license, it's not impossible that they might chose a more locked-down Apple-esque approach for Surface, writes blogger Brian Proffitt. 'And that could put free software for end users very much at risk.'"
A post for some anti-Microsoft tinfoil hat? Must be a slow news day.
It's not Apple locking out GPL, its the GPL locking out the App Store.
+1. I was aboout to post the same thing. This is a BLOG that is filled with nothing but speculation to induce fear, uncertainty, and doubt about what Microsoft MIGHT do to lock-out devices. It was a waste of my time to read. 1/10 stars.
The final paragraph should have been the /. summary: "Free software won't completely go away, of course. There's too much back-end functionality in too many IT sectors for that to ever happen. But with the rise of thin clients and the app store gateways, end users may have a harder time finding and installing free software for their personal or business use."
My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
tl;dr: "they are could be closed devices"
This typo is a good summary of the article.
Perfectly good vocalizing about the death of open systems.. except that it hasn't happened yet has it. Wake me up after the product launch.
If you look at some of the MS SDK licenses, redsitributables and similar things, you often find a clause refering to 'identified software' - here's an example, taken from the ASF/WMA/WMF specification license (http://read.pudn.com/downloads3/sourcecode/multimedia/9891/ASF%20Specification%20v.1.0/ASF%20Specification%20v.1.0.doc, abridged for clarity):
...your license rights to the Specification are conditioned upon your (a) not distributing the Implementation in conjunction with Identified Software (as defined below); (b) not using Identified Software (e.g. tools) to develop the Implementation; and (c) not distributing the Implementation under license terms which would make the Implementation Identified Software. ... Identified Software includes, without limitation, any software that requires as a condition of use, modification and/or
distribution of such software that other software distributed with such software (x) be disclosed or distributed in source code form; (y) be licensed for the purpose of making derivative works; or (z) be redistributable at no charge"
"2 (g)
The details vary between different licenses.. The most restrictive, those on things like the ASF specification that I used as an example, prohibit even using 'Identified Software' at any stage in the development process.
Translated roughly from legalese, this means that if your software is open source or even if you allow users to redistribute it, you aren't even allowed to put it on the same CD as a microsoft redistributable. If you use one of the affected SDKs or licensed specifications that takes the most restrictive variation then you are not only prohibited from releasing your source, or allowing others to redistribute your software, but you can't so much as use vim or emacs to edit your code or GCC to compile it. I also find almost the same clause in things like the Windows XP Embedded EULA, so if you make a product which depends upon XP Embedded then you are not able to open-source the application software that you wrote to run on it.
If Microsoft were to go full-on Evil Empire once again, this is exactly the clause they would probably adapt. All they'd need to do is pass a policy that no 'Identified Software' be permitted in the marketplace. A trivial legal change, and it would easily and effectively not merely bar open source software from the market (And thus Windows RT entirely, as well as use of the metro interface), but possibly even prohibit any Windows dev hoping for commercial success or any accessibility to the ARM mobile users from even utilising open-source development tools.