View Single Post
nthn's Avatar
Posts: 764 | Thanked: 2,889 times | Joined on Jun 2014
#85
Originally Posted by nodevel View Post
I (we) understand what you mean, so you should spare multiple posts.

This is what I think: When OOM kills an app on a phone with 1GB RAM (when no such things would happen years ago on a phone with 256 RAM), then it is a big problem. I would rather have this problem solved with optimization, than hiding the problem by keeping its cover.

So yes, I would like to see this functionality reverted before final Sailfish UI 2.0 comes out - if an app crashes, then I want to see it and deal with the problem, not have it hidden like on Android and other non-multitasking operating systems.

EDIT: I understand that keeping its cover helps keeping other covers in their positions, but I think that this functionality can be easily misused as a mean to have Android-like "single-tasking".
Software grows larger as time goes on. You cannot honestly compare things from years ago that ran well on a low amount of resources with things now. Sure, you can program it all in assembly and you'll have an entire OS + all applications running on 4MB RAM, but there's a reason this doesn't happen. If an application takes up a lot of memory, there are two reasons, either it is not optimised enough or it is optimised but simply has lots of functions. The only solution to apps being killed by OOM (again, this has been the case before 2.0 as well, I fail to understand why it's suddenly an issue again, and why it has to be 'solved' [what would that even entail?] before 2.0 is released to the general public) is to optimise them.

Edit: also, this has nothing to do with apps crashing. If that happens, the cover disappears!
 

The Following User Says Thank You to nthn For This Useful Post: