Tweet
@ slickuser
Anyone thinking that ports are a synonym for holes really shouldn't be talking about security. iOS has 65535 ports, Android has 65535 ports, Windows has 65535 ports, and pretty much anything that has a TCP/IP stack has 65535 ports! Typical non-geek mentality, thinking you understand technical details when you don't.And holes, well, also every OS has holes. iPhone had holes (remember the one that let attackers control an iPhone using SMS?), Android had holes, and so on. It's just about how the vendors handle them. All holes get fixed eventually, regardless of where they are.
Also, multitasking? Oh please tell me, how exactly is multitasking on iOS different from any other multitasking? I read the iPhone multitasking page on Apple's website [1], and frankly, I'm confuzzled. Here's a quote:
"Now you can run your favorite third-party apps ? and switch between them instantly ? without slowing down the performance of the foreground app or draining the battery unnecessarily.* This smarter approach to multitasking is available only on iPhone."
Here's a problem with the over-simplifying approach Apple takes to explaining things, people who actually understand technical details (or geeks, as you call them) are left with absolutely no clue. They won't drink the Kool-Aid without knowing the technical details. What the website says is just propaganda, it has pretty much no meaning.
Now, I am left with vague details and have to deduce what it really does. My assumption is, when you switch from an application to another one, the application receives an event and it has the option to either shutting itself and maybe saving some data to storage (which is the current behavior in iOS), this reduces battery consumption and improves performance. The other option is to keep running some code in the background, a music player for example, and the program will be kept in memory.
Surprisingly, this is what Android does, and Windows Mobile before it. But they kept the program in memory by default, the program had to explicitly say that it wants to be shut down when closed. The only difference I can see is that Apple will seriously limit what a program can do in the background, and will reject any app that it deems 'too battery-intensive in the background', or even add a term to its infamous iPhone Developer Program License Agreement .
[1] http://www.apple.com/iphone/features/multitasking.html
Webmaster Forum | SEO Forum | Coding Forum | Graphics Forum</b>
Anyone thinking that ports are a synonym for holes really shouldn't be talking about security. iOS has 65535 ports, Android has 65535 ports, Windows has 65535 ports, and pretty much anything that has a TCP/IP stack has 65535 ports! Typical non-geek mentality, thinking you understand technical details when you don't.And holes, well, also every OS has holes. iPhone had holes (remember the one that let attackers control an iPhone using SMS?), Android had holes, and so on. It's just about how the vendors handle them. All holes get fixed eventually, regardless of where they are.
Also, multitasking? Oh please tell me, how exactly is multitasking on iOS different from any other multitasking? I read the iPhone multitasking page on Apple's website [1], and frankly, I'm confuzzled. Here's a quote:
"Now you can run your favorite third-party apps ? and switch between them instantly ? without slowing down the performance of the foreground app or draining the battery unnecessarily.* This smarter approach to multitasking is available only on iPhone."
Here's a problem with the over-simplifying approach Apple takes to explaining things, people who actually understand technical details (or geeks, as you call them) are left with absolutely no clue. They won't drink the Kool-Aid without knowing the technical details. What the website says is just propaganda, it has pretty much no meaning.
Now, I am left with vague details and have to deduce what it really does. My assumption is, when you switch from an application to another one, the application receives an event and it has the option to either shutting itself and maybe saving some data to storage (which is the current behavior in iOS), this reduces battery consumption and improves performance. The other option is to keep running some code in the background, a music player for example, and the program will be kept in memory.
Surprisingly, this is what Android does, and Windows Mobile before it. But they kept the program in memory by default, the program had to explicitly say that it wants to be shut down when closed. The only difference I can see is that Apple will seriously limit what a program can do in the background, and will reject any app that it deems 'too battery-intensive in the background', or even add a term to its infamous iPhone Developer Program License Agreement .
[1] http://www.apple.com/iphone/features/multitasking.html
Webmaster Forum | SEO Forum | Coding Forum | Graphics Forum</b>