3 ms·

A) I am an engineer, and at my previous company almost every engineer (9/10) had an iPhone. You should also know better than to insinuate that Elon Musk, Mark Z

by yladiz 9y ago

A) I am an engineer, and at my previous company almost every engineer (9/10) had an iPhone. You should also know better than to insinuate that Elon Musk, Mark Zuckerberg, or Eric Schmidt aren't engineers, considering the companies they've created. B) Citation needed. C) What are the two reasons, specifically? The biggest argument I hear about using Android is that it's customizable, but I would argue that 99% of people, engineers or not, wouldn't customize their phone enough to matter. I would much rather get an iPhone because, even disregarding or accepting the customizability argument, iPhones are less intrusive on your life (I don't want Google to know where I am at all times or know my phone habits), and get updates and work years after they are released. Those two objective reasons alone are enough to warrant me buying an iPhone.

erikb 9y ago
Look. Think about a guy. He stands behind a horse. The horse kicks him in the face. For most people this would hurt. But he doesn't process that feedback. How do you explain to him that it's a bad idea to get close to that horse from its back side? If you can show me a strategy, maybe I can explain to you why iPhones are badly designed. it should be obvious by using it. Examples: a) you get a notification that you have a new mail, whatsapp message or similar. You open the app. Only then the App is able to actually start downloading the content. This is an example of Apps not really being able to work in the background. 80% of what you want to do with a computer you can't do with an iPhone. b) The keyboard has no features to write more quickly, e.g. by swiping. Also the suggestions aren't learning from your input. This means each interaction is very painful instead of being done quickly. c) Click on a Youtube link in FB or Twitter. It will not open the Youtube App, but it will open an app internal browser. From there you can manually redirect to the browser and only then you can open it in Youtube. There is no real event mechanism, or it isn't opened to App developers. d) The costumizability results in you being protected by default, because App developers already have more freedom to provide sane defaults. Even if you never use customizibility yourself, you already gain from it.
- yladiz 9y ago
  Have you used iOS or are you making assumptions based on what you think you know? If it was obvious why iOS was badly designed then I wouldn't have to ask. a) It depends on how the app works but in general you are right. But this is to save data, especially in cases where there are a lot of images. Some apps do download the content when it receives the notification as well. b) Are you suggesting typing is that much more difficult than swiping on a keyboard? Even if that were the case, you can download a keyboard from the App Store that allows you to use a swiping motion on the keyboard. c) That's more Facebook or Twitter's fault for not handling the same events as the built in browser, not the failing of the OS. d) That doesn't make sense. You're protected because app developers have the freedom to provide sane defaults? What about the bad actors that don't provide sane defaults or add malware? I'd rather trust the OS to enforce sane defaults than trust the app developer to, because at least the people that make the OS are generally competent, whereas app developers are more likely to not be.
- dep_b 9y ago
  a) Then push notification itself has a JSON data structure, if you need to prefetch more than that (movies, e-books) a silent push will start a background process specifically designed to do just that. b) Custom keyboards are a thing for at least three generations of iOS c) It's entirely possible to open an application from a webpage d) pure horse shit. In iOS you could prevent applications from reading your contacts from the get go. Until recently permissions were an all or nothing thing in Android. Trusting app developers to respect your or other app developers interests is like trusting a crack head with your credit card. Poor battery life was one of the direct results. It's really no mystery why Google is slowly moving to the iOS side of permissions and background processes.

by yladiz 9y ago

erikb 9y ago

Look. Think about a guy. He stands behind a horse. The horse kicks him in the face. For most people this would hurt. But he doesn't process that feedback. How do you explain to him that it's a bad idea to get close to that horse from its back side? If you can show me a strategy, maybe I can explain to you why iPhones are badly designed. it should be obvious by using it. Examples: a) you get a notification that you have a new mail, whatsapp message or similar. You open the app. Only then the App is able to actually start downloading the content. This is an example of Apps not really being able to work in the background. 80% of what you want to do with a computer you can't do with an iPhone. b) The keyboard has no features to write more quickly, e.g. by swiping. Also the suggestions aren't learning from your input. This means each interaction is very painful instead of being done quickly. c) Click on a Youtube link in FB or Twitter. It will not open the Youtube App, but it will open an app internal browser. From there you can manually redirect to the browser and only then you can open it in Youtube. There is no real event mechanism, or it isn't opened to App developers. d) The costumizability results in you being protected by default, because App developers already have more freedom to provide sane defaults. Even if you never use customizibility yourself, you already gain from it.

yladiz 9y ago
Have you used iOS or are you making assumptions based on what you think you know? If it was obvious why iOS was badly designed then I wouldn't have to ask. a) It depends on how the app works but in general you are right. But this is to save data, especially in cases where there are a lot of images. Some apps do download the content when it receives the notification as well. b) Are you suggesting typing is that much more difficult than swiping on a keyboard? Even if that were the case, you can download a keyboard from the App Store that allows you to use a swiping motion on the keyboard. c) That's more Facebook or Twitter's fault for not handling the same events as the built in browser, not the failing of the OS. d) That doesn't make sense. You're protected because app developers have the freedom to provide sane defaults? What about the bad actors that don't provide sane defaults or add malware? I'd rather trust the OS to enforce sane defaults than trust the app developer to, because at least the people that make the OS are generally competent, whereas app developers are more likely to not be.
dep_b 9y ago
a) Then push notification itself has a JSON data structure, if you need to prefetch more than that (movies, e-books) a silent push will start a background process specifically designed to do just that. b) Custom keyboards are a thing for at least three generations of iOS c) It's entirely possible to open an application from a webpage d) pure horse shit. In iOS you could prevent applications from reading your contacts from the get go. Until recently permissions were an all or nothing thing in Android. Trusting app developers to respect your or other app developers interests is like trusting a crack head with your credit card. Poor battery life was one of the direct results. It's really no mystery why Google is slowly moving to the iOS side of permissions and background processes.