• Ephera@lemmy.ml
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    4 months ago

    Yep, I also don’t fully agree on that one. I’m typing this on a degoogled Android phone with quite a bit stronger hardware than the iPhone SE that my workplace provides, e.g. octacore rather than hexacore, 8GB vs. 3GB RAM.

    And yet, you guessed it, my Android phone feels quite a bit laggier. Scrolling on the screen has a noticeable delay. Typing on the touchscreen doesn’t feel great on the iPhone either, because the screen is tiny, but at least it doesn’t feel like I’m typing via SSH.

    • uranibaba@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      That has to be because the code is better optimized for the hardware in case of iPhone and less so which language it was written in.

      • Ephera@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        Why? I certainly expect that to be a factor, but I’ve gone through several generations of Android devices and I have never seen it without the GC-typical micro-stutters.

      • Ghoelian@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        4 months ago

        I have experienced the delayed scrolling, mostly on cheaper phones.

        But that’s mostly because i’m used to phones having 120+hz screens now, going back to a 60hz screen does feel a bit sluggish, which is especially noticeable on a phone where you’re physically touching the thing. I think it might also have something to do with the cheaper touch matrixes, which may have a lower polling rate as well.