Born and raised in London. Just a normal guy with a moral compass.

  • 163 Posts
  • 740 Comments
Joined 1 year ago
cake
Cake day: March 16th, 2024

help-circle




  • As I said, I have a low memory device so I’m talking from experience.

    In fact Google itself says that devices with less than 6GB of RAM should be running Android Go rather than Android 16.

    Honestly, devices designed to be obsolete are a pain for everyone. We need devices that are designed to be usable in a few years, that means shipping them with decent processors, memory and storage. By Android 17, the minimum memory requirement is likely to be 8GB and there’s going to be a bunch of people wondering why some apps, the more complex ones like browsers, don’t run smoother.

    Maybe a solution is that Firefox starts serving older devices an ESR.



  • Okay, that’s the problem. 4GB of RAM isn’t enough for modern Android. I know because it’s what I have on my tablet and it’s bullshit, if I use certain apps, others in the background are force closed, etc. All I can say is that with some of the changes taking place with the switch to Jetpack Compose, Firefox is getting better in terms of a smaller memory footprint, but that’s little consolation for you now and your urgent/present needs.

    BTW, well done for using a private DNS for stopping the problem at the root.






















  • I agree with @Illecors@lemmy.cafe . The whole argument in the article is that unfamiliarity is scary. Despite the fact that all other Google products follow a similar model. Google have made it so that Canary is omnipresent and they can drop in and out features as they want for testing. The article writer is like, but at least the old way, we were sure. Even though there’s plenty of times things have come and gone for QPR’s and Developer Previews. It’s moaning for the sake of moaning and now saying very much. It’s actually embarrassing that the author got paid for such an article.