Active Topics

 


Reply
Thread Tools
Guest | Posts: n/a | Thanked: 0 times | Joined on
#91
Originally Posted by Bundyo View Post
On the plus side the browser is accelerated and lightning fast
um... you sure about that? your account counters a lot of others I've seen, so what sites are you comparing it to, what not?
 
Bundyo's Avatar
Posts: 4,708 | Thanked: 4,649 times | Joined on Oct 2007 @ Bulgaria
#92
Probably because I messed up the first time and had to reset However now for me it runs much faster than before.

Also I don't have some issues other people have reported like the slow wake up for instance. I like most of the changes too
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
 
Posts: 752 | Thanked: 2,808 times | Joined on Jan 2011 @ Czech Republic
#93
Originally Posted by Makeclick View Post
Way that pulldown menu looks... It's not that sweet, but i actualy like that 2time flicks, when you select something
Well, I actually don't mind the looks that much, but I didn't like the new delay and 2 blinks (it really slows things down), so that's why I present a new patch:

Faster Pulley Menus

It feels much smoother now, but that's just my opinion
 

The Following 10 Users Say Thank You to nodevel For This Useful Post:
Posts: 168 | Thanked: 143 times | Joined on Nov 2012
#94
Originally Posted by nodevel View Post
Well, I actually don't mind the looks that much, but I didn't like the new delay and 2 blinks (it really slows things down), so that's why I present a new patch:

Faster Pulley Menus

It feels much smoother now, but that's just my opinion
...Aaaan installed within first 10 seconds
 

The Following User Says Thank You to parasemic For This Useful Post:
Posts: 1,548 | Thanked: 7,510 times | Joined on Apr 2010 @ Czech Republic
#95
Originally Posted by pichlo View Post
Indeed there is a reason. It can be described in just two words:
1) lazy
2) programmers
While you are mostly correct (at least to about ~95% of cases - many people really do write horrendously inefficient code), its not true in all cases. There are valid cases why software might be more resource intensive now then before:
  • various security & hardening related features might make stuff more resource intensive while making applications more secure and harder to exploit/attack
  • more robust range checking - more or less directly related to the point above, you can prevent undefined or directly exploitable application behavior by stricter range memory usage checking at cost of some processing & memory usage - an ideal program of course does not need this and would run faster and with less memory usage without it, but humans hardly write ideal programs on a regular basis
  • localization and accessibility - a hardcoded-to-English app without accessibility would be of course be a bit faster, but harder to use for people that are not native English speakers and/or have various disabilities
  • bigger screens and advanced graphical/usability operations - modern computer screens are much larger than before, meaning larger bitmaps, larger framebuffers, etc.; applications might also opt to use transitions or other visual cues to make the UI more fluent (eq. stuff animates to place vs just blink in place without any transition) which can again cost some performance
  • optimizations - programs can opt to actually make use of all that available RAM/CPU power to do CPU/memory usage trade-offs that actually make the application faster at the cost of bigger resource consumption - of course there should be a way to dial down or outright disable these optimizations when running in a resource constrained environment
  • introspection and debugging information - you can make your data structures slightly bigger by adding additional information that is not strictly needed for your application, but which can be used by other tools to either make better use or your code (if you are a library an example can be the GObject Introspection, which can generate language bindings automatically, as an example) or might aid with application debugging (GTK inspector can be seen as an example, or improved crash tracebacks, etc.)
  • portability - an application written for a single combined software and hardware platform can make a lot of assumptions that improve performance - at the cost of making the application very hard to port to other platforms; a multi-platform application needs to make much less assumptions, needs to do many checks at runtime and often uses slightly less efficient techniques/APIs that are platform independent in place of faster but platform specific ones to aid long term maintenance
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
 

The Following 7 Users Say Thank You to MartinK For This Useful Post:
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#96
Originally Posted by Bundyo View Post
The expectation that what you left is still there.
Exactly. A very slippery road if this is already being done. Over Android and iOS behavior (which is basically the same these days) I would very much prefer copying the behavior from actual "multi tasking first" UIs, like webOS or Maemo, which basically prevent me from opening "too many cards". But that is even more complicated and I don't think it is necessary.

IMO, I would just do dynamic swapspace and let things sort out by themselves. Sadly, I believe the version of Jolla's btrfs seems to have problems with swap files.
 

The Following 6 Users Say Thank You to javispedro For This Useful Post:
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#97
Originally Posted by MartinK View Post
While you are mostly correct (at least to about ~95% of cases - many people really do write horrendously inefficient code),
Aaand no one cares about the 5%, when there's that "problematic 95%" (Amdahl 's law).

I don't hink the numbers are correct either way, just pointing out that it's a "several orders of magnitude" thing.
 

The Following 4 Users Say Thank You to javispedro For This Useful Post:
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:
Bundyo's Avatar
Posts: 4,708 | Thanked: 4,649 times | Joined on Oct 2007 @ Bulgaria
#99
Originally Posted by aegis View Post
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.
Not sure about that. There is no clear indicator that a task is dead. It does show you a screenshot from the time when it was live and the blurriness probably comes from that it isn't done very well.
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
 

The Following 2 Users Say Thank You to Bundyo For This Useful Post:
Jordi's Avatar
Posts: 400 | Thanked: 708 times | Joined on Jun 2011 @ Geneva - CH
#100
Originally Posted by Bundyo View Post
Not sure about that. There is no clear indicator that a task is dead. It does show you a screenshot from the time when it was live and the blurriness probably comes from that it isn't done very well.
I hope you're wrong and the bluriness is done on purpose!
 

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


 
Forum Jump


All times are GMT. The time now is 23:16.