3 ms·
> Holding the phone manufacturer responsible for code I wrote is not in fact a natural thing to do. I'm sorry but I'm really struggling to understand what you
by lucideer 7y ago
> Holding the phone manufacturer responsible for code I wrote is not in fact a natural thing to do.
I'm sorry but I'm really struggling to understand what you mean by this. What hardware should I be running the code I write on without fear of voiding the warranty.
If it's the fact I wrote the code that constitutes voiding the warranty, exactly who's code should we be permitted to run on hardware we've purchased? Only code which has been written by/provided by the manufacturer themselves?
What's the precedent for this absurd restriction?
- thaumasiotes 7y agoYou shouldn't be running the code you write on any hardware without fear of voiding the warranty. The point of a general-purpose computer is that the code you write might do anything at all. There is no warranty to cover that, and there shouldn't be. You should get over your desire for a warranty.
- Macha 7y agoWhy is this acceptable for the computers that go in our pockets when its clearly not the case for those that go in our backpacks or datacenters?