Microsoft Tries to Patent a Crippled Baseline OS
Microsoft is applying for a patent for an operating system that starts out crippled. You must pay to do things like take the throttle off network speed, disk access, install drivers, install software, and more. Trust me, I rarely even visit Groklaw, even if this is my second consecutive blog entry with a link to a Groklaw article. My VarLinux.org readers posted the article, A Brave New Modular World, and I had to share it.
As the article states, the fact that Microsoft is attempting to patent a cripple technique isn't the real story. It is more likely Microsoft is applying for this patent in order to float the idea and see what kind of reaction it gets. Regardless, if Vista is any indicator, it seems very realistic that the next version of Windows will implement something like this. Vista already shifts into throttled cripple mode if it detects what it believes is pirated video. The idea behind this patent is that the next Windows could start in cripple mode, and the only way to get it to perform normally is to pay Microsoft to unlock "features" that most right-thinking people assume the operating system should provide by default.
The article paints a scenario where this could actually discourage people from switching to Linux from Windows. After all, Dr. Stupid opines, if you pay for a 3 year subscription to unlock the throttling and get access to updates, you'd want to get your money's worth and stick with Windows for 3 years.
Here's a question for you: Assuming Microsoft follows through with this plan or something like it, do you think this would really lock people in? Or would it drive people to Linux (or just about anything else besides Windows)?
(Disclaimer: VarLinux.org is totally non-profit, and I have no association with Groklaw, so the links are not obfuscated plugs.)
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- August 2015 Issue of Linux Journal: Programming
- Hacking a Safe with Bash
- Django Models and Migrations
- Secure Server Deployments in Hostile Territory, Part II
- Huge Package Overhaul for Debian and Ubuntu
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- KDE Reveals Plasma Mobile
- Embed Linux in Monitoring and Control Systems
- General Relativity in Python