viewWillUnloadand decided that ultimately the memory hit from releasing objects in these methods wasn't enough of a concern to keep those methods and they were deprecated. It was basically a nice way of saying that a lot of developers are so terrible at view lifecycle management that they were just going to remove the unload methods so that developers didn't continue to mess up their app by not knowing what they were doing. Now I personally applaud Apple for taking into account this problem and dealing with it in a way that doesn't hurt legacy apps. However, I do believe that all APIs are tools that when wielded appropriately can be useful for building something that works well. So when
viewWillUnloadwere deprecated, one of the first things I set out to do was port them so that I could continue to use these "tools" into the future. Now, if you don't want to use
viewWillUnloadand want to conform to Apple's recommended application life cycle design guidelines then this article won't likely help you, and I must credit your wisdom. For the rest of you, let's jump into memory warnings!