| ▲ | nemomarx 8 hours ago | ||||||||||||||||
You shouldn't be remotely disabling hardware features in my opinion at all. It's not really like changing an API or something, this is like an update removing something from your car or another appliance years after you bought it. | |||||||||||||||||
| ▲ | fc417fc802 4 hours ago | parent | next [-] | ||||||||||||||||
> You shouldn't be remotely disabling hardware features I don't know what current case law is but I think that ought to be explicitly illegal. A physical product should be required to maintain the features that it had when it was purchased. Anything else is clearly cheating the consumer. | |||||||||||||||||
| ▲ | embedding-shape 8 hours ago | parent | prev [-] | ||||||||||||||||
Yeah, basically you'd trade uncertainty for the ability to remotely enable/disable hardware features not ready at launch I understand, which totally makes sense as a position, I probably agree with you. I think from AMD's side they like the option of being able to remotely enable things though, so new software updates in the future could be major releases enabling functionality that wasn't quite ready at launch. But, I suppose the uncertainty is the tradeoff here. | |||||||||||||||||
| |||||||||||||||||