Google ne devrait pas rouler 64-bit versions d’applications de périphériques que hav…

Google should not roll out 64-bit versions of apps to devices that have less than 6 GB of RAM

Avant d’acquérir un smartphone pliable, il faut absolument regarder les différents appareils disponibles sur le marché. Lequel, permettra vraiment de lire les blagues tous les jours de manière confortable ?

aussi excité que je suis pour apps transition vers 64-bit de cet été, je suis préoccupé parce que l’expérience utilisateur est la chose la plus importante et de ma propre expérience et de ce que j’ai entendu des autres, un téléphone devrait probablement avoir au moins 6 Go de RAM si ça va exécuter les applications 64 bits. Nous avons déjà un certain Pixel 3 utilisateurs disant 4 Go n’est pas suffisant, et les applications 64-bit fera cette situation encore pire. Quelles sont vos pensées et opinions là-dessus ?

Edit : 6GO est peut-être trop élevé. Que diriez-vous de 4 Go minimum pour les applications 64 bits ?


Voir sur Reddit by jasonrmns

13 réflexions au sujet de “Google ne devrait pas rouler 64-bit versions d’applications de périphériques que hav…”

  1. I don’t think using 32-bit apps would have helped with the Pixel 3’s issue anyways. It is simply due to the memory management for that phone and Google has already worked on fixing it and can continue to tweak it with software updates.

  2. Considering how Android and the underlying Linux kernel handle memory, there is no need for this sort of limitation. Then there’s the bit about 32 bit and 64 bit systems having extremely similar RAM needs. What I wonder is exactly how you came to the conclusion that anything less than 4-6 gb of RAM would affect performance.

  3. I think you didn’t quite understand what the change is – most modern flagships are already running 64-bit images so nothing will change for them. This includes all Pixels.

    The change is about forcing developers to add 64bit native cover if they’re using it which gives you more performance. Apple did a full switch on 2GB devices and it was fine.

  4. Spec sheet babies will always bring this up. I’m a Google fanboy but Google didn’t shit the bed by making it a 4 GB of RAM phone – they shit the bed by poorly optimizing it. No amount of RAM is worth a shit if it’s not optimized.

  5. If a free app is slow or crashing, just don’t use it.

    Better yet, if it’s open source, help improve it.

    If it’s a paid app, ask for a refund or a fix.

    not 64-bit’s problem

  6. 4GB of RAM was never a limitation on my HTC 10. Battery started to go crazy, so I upgraded to pixel 2XL last year. No issues there either with same RAM. I upgraded to the Pixel 3XL during the Black Friday and also have no issues with the 4GB of ram. I haven’t experienced any of the bugs people have either before or after the last March update. In any case, I don’t think those issues are RAM related, but hardware related. These phones might be faulty. I can switch between 8-11 apps depending on the apps without reloading, so I’m thinking I lucked out on the Google quality lottery. I see no complaints from other manufacturers with 4gb of ram. That is a LOT of ram for a mobile device.

  7. I remember this argument a decade ago on PCs. I’ve been using 64 bit OSes since 2007, on PCs with as low as 1 GB of RAM, and it’s always been fine. My rule was always that if the CPU supported 64 bit, I will use a 64 bit OS (and apps). I think for phones that should apply too.

    I think any memory issues with phones is due to either bloated apps (which is a problem regardless of CPU architecture), people trying to do too much with the RAM they have, or poor memory management on the OS side (I believe this is a legitimate issue on some phones, I have seen it myself).

  8. A full Linux distribution runs without crashing and reloading your programs with 4GB, Windows can run (with speed difficulties though) with 4GB, you never see a single app crasing and reloading even by multitasking a lot, so no what Google must do is optimizing the system, its apps and beginning a dev program to penalize apps using a lot of RAM

Les commentaires sont fermés.