Thread: First thoughts about the (pre) Sailfish OS 2.0
View Single Post
aegis is offline aegis
2015-09-08 , 01:10
Posts: 702 | Thanked: 2,059 times | Joined on Feb 2011 @ UK
#98
Originally Posted by nodevel View Post
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.
256MB? Luxury! I've a Mac SE30 in the office and with 4MB it runs email, SSH, ftp and even a web browser (slowly) and switches between them.

Originally Posted by nodevel View Post
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.
If it crashes then it should tell you it has crashed. That's what Android does. It pops up a dialogue telling you it has ended.

If Android has killed the task because it is no longer needed or because of OOM then it leaves a card in the task list. Sailfish 2.0 seems to be doing exactly the same thing as Android here except you can tell which tasks are live and which are closed.

Originally Posted by nodevel View Post
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".
I think you're grossly misunderstanding how Android multitasks. Try reading http://www.extremetech.com/computing...ndroid-and-ios
 

The Following 6 Users Say Thank You to aegis For This Useful Post: