Thread: First thoughts about the (pre) Sailfish OS 2.0
View Single Post
gerbick
2015-09-07 , 16:55
Guest | Posts: n/a | Thanked: 0 times | Joined on
#83
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".
While great, this doesn't take into consideration code bloat. From my understanding, Jolla/Sailfish is highly optimized, but people just rarely code tightly now.

So from my understanding, this is a dislike on how multi-tasking apps act once either: RAM runs out or upon error, how that app is handled by the OS. The way Android does it, isn't liked, I get that. Until we get to see how Sailfish handles two apps on the screen at once, I'd say that you're still stuck with serial tasking in most apps that are sent to the background anyway since you're not truly interfacing them at the same time.

That's my take, probably inaccurate but as far as it stands, this is not really a big issue unless this affects native audio & video apps that are in the background.
 

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