We aren't arguing the same thing. The post I responded to appeared to me to claim that Apple should honor warrantees on jailbroken phones; the argument is that Apple should design hardware so good that software can't possibly destroy it. I was refuting that claim, not addressing bricking caused by jailbreaking.
But you buy the -hardware- unless you are overclocking the CPU or something, they should have to allow warranty claims for hardware issues. Just because I run Linux on my laptop, if the screen dies, I expect the hardware company to pay for it if it is under warranty. Granted, if I try to install RAM that isn't compatible with the system and I break the sockets, of course the hardware company shouldn't have to pay for it.
No matter what you do with the software, it shouldn't ever break hardware barring overclocking and the like and so they should still have to allow claims for hardware issues.
What you want is for Apple to invest money to make sure their hardware is fault tolerant against buggy software that hasn't even been written yet. Software that could only be installed by deliberately escaping the insulated ecosystem they already invested money building.
You're perspective is way off. And I'm by no means a fanboy.
Con? Is that you?
There are other licenses outside of the GPL that the FSF considers fully free, in that they force users of the code to extend the same freedom they were given unto others.
Again freedom only what the FSF defines as freedom.
Your point? The FSF considers BSD licenses free as well, but their preference is for the GPL and its ilk.
Yes because freedom is having one person define what freedom means.
OMFG, in the last 18 years or so, something has been itching at the back of my head after hearing RMS speak. I've been following the whole GPL, BSD, etc. BS for awhile. Something kept nagging at me and I couldn't find the words for it.
You're post, screaming for a true implementation of a sarcasm tag, just wrapped up the whole thing for me. You have provided my new sig line.
To be honest, it's a weak argument against the FSF's version of freedom.
There are other licenses outside of the GPL that the FSF considers fully free, in that they force users of the code to extend the same freedom they were given unto others.
Yes, it's clearly a mistake. But it's not likely the cause of an engineer "forgetting" that our hands are conductors. You missed my point completely.
A systems engineer that designs the specs needed for an antenna will take in to account a lot of things, including (in this case) attenuation from your hand.
It's not a case of the engineers not knowing that your hand is a conductor; it's not correctly measuring/characterizing the end to end signal quality needed for adequate reception.
It's Obama's fault that this mistake caused by corporate greed and cost cutting wasn't fixed weeks ago.
Whoosh.
Imagine a dystopic future where the cruel masterminds that rule our society steal ideas from science fiction writers to aid them in their domination of mankind.
Yeah -- someone should write a science fiction piece about that as a warning.
Owait we just did.
See how this works?
I get what you are saying there, but I'm still confused.
I originally made a joke about the thought of a corrupt government getting ideas from dystopic science fiction authors. You then explained the point of science fiction, and I felt like you didn't get the joke.
Did you layer on a joke in your original response that was more subtle than I could detect?
Whoosh.
Imagine a dystopic future where the cruel masterminds that rule our society steal ideas from science fiction writers to aid them in their domination of mankind.
... you're giving them ideas!
Also, if they're successful (God help us if they are), future lawsuits will be cut and dry.. and hence cheap. This is probably viewed as an initial investment or non-recurring expense for the RIAA.
I don't see the legal protection, they have to spend millions of dollars to maybe establish a precedent. It's not like they're buying the legal precedent; they're merely bankrolling a legal campaign to get it in front of a judge for a chance at precedent.
Yeah, cc is common for me. I use "index" in ruby and javascript, because it describes exactly what the variable is. In C, though, I will use 'cc' or 'xx'.
Have you tried the shiv technique mentioned in TFS?
Systems programmers are the high priests of a low cult. -- R.S. Barton
