marahmarie: (M In M Forever) (0)
MM Writes ([personal profile] marahmarie) wrote in [personal profile] mjg59 2016-09-24 04:18 am (UTC)

Your reply is, at best, disingenuous. I mean, tell me you've never overclocked a CPU, or that you don't at least know how to. Yet you write:

Why should it be up to the user?


OK, so why not, if I paid for the damn thing?

Should the user be able to program every memory timing option, even if by doing so they introduce occasional crashes?


Oh, hell yes, if I paid for the damn thing.

Should they be able to set every thermal threshold, even if by doing so they're reducing their hardware life expectancy?


Yes! I paid for the damn thing, so if I void the warranty, that's on me; no one else's concern.

All hardware vendors restrict the options available to users.


Doesn't mean they should. I had an eMachines years ago I couldn't overclock to my endless frustration, since it had long been out of warranty by then. My problem should I want to, not anyone else's.

I normally defer to your opinion because you actually know more than I do about a lot of the topics you cover here, but this post's just squirrelly, between the unconfirmed statements you pulled from ZDNet and the sudden idea you seem to have that our tampering should be kept to a minimum on machines we bought and paid for ourselves.

I mean, you can't say to a roomful of tinkerers "should you be allowed to do so much tinkering" and expect it to go over well, because obviously it's not.

Post a comment in response:

If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org