Re: First thoughts about the (pre) Sailfish OS 2.0
 

How should it change? What difference in a negative way do you perceive compared to previous Sailfish versions?

Edit: of course apps being killed while in the foreground should never happen, but this in itself has nothing to do with the covers.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

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".

Re: First thoughts about the (pre) Sailfish OS 2.0
 

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.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

Well, if an app crashes a crash handler (such as ABRT used in Fedora/RHEL/CentOS) should show up and ask the user if he wants to report the crash (user writes what caused the crash and confirms what logs to send), so that the application developers know about the crash and can do something about it. :)

Much better for all parties than having to report all crashes manually.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

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!

Re: First thoughts about the (pre) Sailfish OS 2.0
 

On the plus side the browser is accelerated and lightning fast :)

Re: First thoughts about the (pre) Sailfish OS 2.0
 

The expectation that what you left is still there. ;)

Re: First thoughts about the (pre) Sailfish OS 2.0
 

Indeed there is a reason. It can be described in just two words:
1) lazy
2) programmers

And yes, I am speaking from experience. I am a programmer myself and the way I see my fellow programmers waste resources pains me to no end. The algorithm runs too slowly or runs out of memory? Why bother investigating the cause, just give it a higher priority or allocate a bigger buffer!

Unfortunately I see this kind of attitude everywhere, its application in programming is that, one application out of many. Other examples: driving in the middle lane of an empty three-lane motorway... a group of three taking a table for 6 when smaller tables are available... buying a bigger pack of yoghurt in the full knowledge that you will never finish it and end up throwing it away - but it's only 10% dearer than the small pack, so what?... keeping the fridge door open while pouring the milk in your tea, because who cares, right?

It is this attitude that means that 1GB is not enough for a task that just a few years ago ran happily on 4MB, nothing else.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

"If an application crashes" and "if the OS decides to kill a well behaving application just because" are two different things. Just thought I'd point that out ;)

Re: First thoughts about the (pre) Sailfish OS 2.0
 

I like SailfishOS 2.0 MUCH! Looks and feels so smooth and way easier. Now you can open apps very fast, because you can always swipe from bottom and it stays on top. Now it feels multitasking phone... Browser lags littlebit still there 3tab max, but now it is fast again!!!

One thing i can't understand.. Why landscape is not ready? It works, but at home screen it will always turn portrail, with nice turn efect :)

Way that pulldown menu looks... It's not that sweet, but i actualy like that 2time flicks, when you select something :)

But thats me. Me like!