4 ms·

I don't think UI is the issue. Coming from someone who WANTS to love android for philosophical reasons and bought the google nexus, google nexus 5x. I always w

by asdf333 10y ago

I don't think UI is the issue. Coming from someone who WANTS to love android for philosophical reasons and bought the google nexus, google nexus 5x. I always went back to iphone. The biggest issue is the device is not very good in comparison to the current gen iphone. It feels 1-2 gen behind in performance.

kaishiro 10y ago
How so, exactly? I have a 5x myself and have never felt this to be the case.
TheLilHipster 10y ago
Eh? I still use a first generation Nexus 5. SNES/N64/PSP emulators run like a dream. Apps open/transition instantly. What performance metric are you even using?
- talideon 10y ago
  In a nutshell: Android itself isn't actually any slower, but it _seems_ slower due to garbage collection pauses. When Android stutters, you can put money on it being down to the garbage collector running at an inopportune moment. This is the downside of most Android apps being built in Java, whereas most iOS apps are written in Objective C, which uses reference counting and so you have more deterministic release of allocated memory. The upside of this is little or no stuttering, but the downside is that you can still end up with pauses, but they can be in places which are hidden from the user. The other downside of GC is that developers can lean on it a bit more than is justifiable to create needless duplicates of objects on the assumption that they'll be garbage collected eventually... which can lead to GC stutter. A lot of Android's 'slowness' issues would go away if devs were a bit more careful with how they allocate their objects. Another thing that makes Android seem slower than iOS is that Android gives apps a pretty lengthy grace period when they hang for some reason and will alert the user if it thinks the app has hung. iOS, OTOH, is less tolerant of this kind of thing and will just kill the offending app and rely on the app to restore its state when restarted. This hides a lot of issues with apps on iOS that are more obvious on Android. Which choice is better is a matter of debate: the iOS route gives the better user experience 90% of the time, but when you want that 10%, you really want that 10%. Emulators (and quite a lot of games too) tend to be written in C and C++, which means they do manual memory management or use the conservative Boehm GC, so you end up with little or no GC stutter. OTOH, if the developer isn't careful, you're more likely to end up with memory leaks.
- tigershark 10y ago
  You must have a lot of nightmares then. My old iphone 4 lasted happily for 4 years and after I gave it to my sister in law. I couldn't force myself to use the awful nexus 5 for even two years. And I really went close to throw that piece of crap against the wall. Apparently the "new" nexus 5x is even slower than that for some reason that is beyond human comprehension. You really have very low performance standard, like my friend that enjoys his Nexus 5x even if it feels like a slo-mo fest compared to my iphone. Good for you, but please don't even try to convince anyone of the super performance of your favourite phone.
  - ubertaco 10y ago
    Lots of anecdotes, and then: > Good for you, but please don't even try to convince anyone of the super performance of your favourite phone ...maybe take your own advice?

by asdf333 10y ago

kaishiro 10y ago

How so, exactly? I have a 5x myself and have never felt this to be the case.

TheLilHipster 10y ago

Eh? I still use a first generation Nexus 5. SNES/N64/PSP emulators run like a dream. Apps open/transition instantly. What performance metric are you even using?

talideon 10y ago
In a nutshell: Android itself isn't actually any slower, but it _seems_ slower due to garbage collection pauses. When Android stutters, you can put money on it being down to the garbage collector running at an inopportune moment. This is the downside of most Android apps being built in Java, whereas most iOS apps are written in Objective C, which uses reference counting and so you have more deterministic release of allocated memory. The upside of this is little or no stuttering, but the downside is that you can still end up with pauses, but they can be in places which are hidden from the user. The other downside of GC is that developers can lean on it a bit more than is justifiable to create needless duplicates of objects on the assumption that they'll be garbage collected eventually... which can lead to GC stutter. A lot of Android's 'slowness' issues would go away if devs were a bit more careful with how they allocate their objects. Another thing that makes Android seem slower than iOS is that Android gives apps a pretty lengthy grace period when they hang for some reason and will alert the user if it thinks the app has hung. iOS, OTOH, is less tolerant of this kind of thing and will just kill the offending app and rely on the app to restore its state when restarted. This hides a lot of issues with apps on iOS that are more obvious on Android. Which choice is better is a matter of debate: the iOS route gives the better user experience 90% of the time, but when you want that 10%, you really want that 10%. Emulators (and quite a lot of games too) tend to be written in C and C++, which means they do manual memory management or use the conservative Boehm GC, so you end up with little or no GC stutter. OTOH, if the developer isn't careful, you're more likely to end up with memory leaks.
tigershark 10y ago
You must have a lot of nightmares then. My old iphone 4 lasted happily for 4 years and after I gave it to my sister in law. I couldn't force myself to use the awful nexus 5 for even two years. And I really went close to throw that piece of crap against the wall. Apparently the "new" nexus 5x is even slower than that for some reason that is beyond human comprehension. You really have very low performance standard, like my friend that enjoys his Nexus 5x even if it feels like a slo-mo fest compared to my iphone. Good for you, but please don't even try to convince anyone of the super performance of your favourite phone.
- ubertaco 10y ago
  Lots of anecdotes, and then: > Good for you, but please don't even try to convince anyone of the super performance of your favourite phone ...maybe take your own advice?