Robin Humble wrote:
after all, how many of us write code that checks the return value of close()? how about checking and re-trying short read() and write() calls?
It irritates me to put "or die" after every line, but I tend to do it (I think). I do miss the feature "hey bash, do 'or die' if any command terminates unsuccessfully (except predicates)" in other languages...
google was likely desperate for apps at the beginning. their app store had nothing in it. even now I'm not sure it was the wrong decision to make... apps asking for too many permissions and then abusing them is the real problem. I don't think it's the permissions model itself.
It seems to me that's a knock-on effect of the original design.
if facebook had open protocols then someone else could write a facebook app that didn't steal your phone number even before you'd logged in. perhaps fighting for open protocols is the real solution.
I don't see how you'll make any headway with that, when it directly contradicts their business model.