Live data from Hacker News

Microsoft Will Eventually Start Charging You for Windows 10 Security Updates

gizmodo.com

1–10 of 92 posts

Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates

#6
Same as usual, they were doing this until just recently with Windows 7 updates

https://learn.microsoft.com/en-us/troubleshoot/windows-clien...

Windows 8 didn't get an ESU program though, I have to assume because it didn't get the adoption of 7 and people mostly moved on to 10.

Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates

#7

Cost to consumer, incentivizes companies to adopt new technology and avoid relying on specific OS versions. Seems like a good policy.

Or force you (the consumer) to upgrade to newer versions with hostile terms of service and/or applications. It works both ways.

Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates

#9
post #3

That's not what security updates are. They are fixes for errors in the original software. They are product recalls for dangerous product faults. You can't charge the customer because the product you shipped them was faulty.

Despite the legal system depending almost exclusively on analogies like this when it comes to tech, I feel that I have read very few legal opinions that make them.

Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates

#10
post #7

Cost to consumer, incentivizes companies to adopt new technology and avoid relying on specific OS versions. Seems like a good policy.

Or force you (the consumer) to upgrade to newer versions with hostile terms of service and/or applications. It works both ways.

This is a really negative take. They could also add hostile terms of service at other times or do hostile things. It's about cost and marketing.

Windows N+1 will share a majority of code with Windows N. Microsoft would now have to maintain two copies of the code N and N+1. This is added cost.

Alternatively Windows could do continuous releases, but this is less fun to market, and users might not like big changes happening many times a year instead of all at once, etc. There are also compatibility challenges for this since behaviors are tagged to such specific versions.

Post reply on HN