Binoya Mathews
New member
Well, in low memory situations if the OS ,in most cases can handle what needs to be done without causing problems to the end user, y is there a problem? I wasn`t exactly referring to memory restrictions there, but about memory management of iOS as a whole .Not you called it a glitch, but a poster a bit above you. I was just being lazy and included references to others in my reply to you. Sorry.
If you'd also explain why you feel Apple's indeterminate approach is superior, which requires all kinds of mechanisms be in place to ensure stability in low memory situations, I'd be happy to hear them.
Y do I say that? we all know unused RAM is wasted RAM. Why do the apps need to stick to these limits if it does not give that much of a benefit to the user/the developer?. If the device goes low on memory, mechanisms are in place in case of iOS which will handle the issues, such as the low memory warnings which is send to the app. The recent iOS release makes things better by prioritising the apps based on usage and time. If u open an app at a time on one day, the next day the app is there is already preloaded, waiting for you to open it up. Similarly, the most used apps are given top priority and allowed to run in the background and thus can launch at once when opened. These things help not only in performance but also help increasing battery life by terminating the apps which are rarely used. Again if necessary, the OS can free up memory while running or performing certain tasks, killing them off ,again UNIX advantage. These things even adapt to network conditions.
On the other hand, you have windows phone which is still having the background processes , yet to be sorted out, even joebelfiore admits they are a mess. That`s what I meant and it wasn`t exactly about this restriction in particular. WP8 developers have a lot of work to be done.