3 ms·

Part of the problem is Java itself, it's too easy to add a 'binary' dependencies in Java, so applications get bloated. Part of the problem is that Google remov

Part of the problem is Java itself, it's too easy to add a 'binary' dependencies in Java, so applications get bloated. Part of the problem is that Google remove the interpreter of Android so and AOT codes creates big executables which need to be loaded in memory. Part of the problem is not Google but the fact that application makers test on flagship phones Pixels, Galaxy etc. Part of the problem is that Google waits too long before introducing Go edition (available since Oreo) which re-introduce the interpreter and provides a clear target. Part of the problem is that low cost smartphones is not where the money is, so there is no real insensitive to target low cost smartphones.

llukas 8y ago
All of those are not a problem if you want to address problem of low memory and design for it.
- soziawa 8y ago
  Sure, but if money is not an issue, why not get them a phone with more memory?
  - benologist 8y ago
    Google's the one dodging taxes and writing bloated crap so why should consumers pick up the tab for bigger hardware? That's subsidizing them for not hiring enough people to do anything but dodge taxes and defraud advertisers, while they hoard over $100b in cash... I think what we should do is make their carbon footprint tally include their shitty javascript all over the internet and their apps on phones.
- squarefoot 8y ago
  forcing software to run under a virtual machine adds one more layer, so no matter how good software can be designed, compared to similarly optimized native software it will always mean more code to be executed, that is, more time needed to execute it and more space needed to contain it. They used the VM approach for security reasons, which to me is terribly wrong. Mobile terminals should have hardware separation between subsystems, that is, the sensitive stuff (radio) enclosed in black hardware boxes where data goes in and comes out, just to make telcos happy, but everything else -I mean all the OS and apps- should be native and user accessible. This way one gets the best possible performance while maintaining a high degree of separation between kernel+userland and radio chipset which would let allow hacking whilst preventing anyone to tamper with cell connectivity.

llukas 8y ago

All of those are not a problem if you want to address problem of low memory and design for it.

soziawa 8y ago
Sure, but if money is not an issue, why not get them a phone with more memory?
- benologist 8y ago
  Google's the one dodging taxes and writing bloated crap so why should consumers pick up the tab for bigger hardware? That's subsidizing them for not hiring enough people to do anything but dodge taxes and defraud advertisers, while they hoard over $100b in cash... I think what we should do is make their carbon footprint tally include their shitty javascript all over the internet and their apps on phones.
squarefoot 8y ago
forcing software to run under a virtual machine adds one more layer, so no matter how good software can be designed, compared to similarly optimized native software it will always mean more code to be executed, that is, more time needed to execute it and more space needed to contain it. They used the VM approach for security reasons, which to me is terribly wrong. Mobile terminals should have hardware separation between subsystems, that is, the sensitive stuff (radio) enclosed in black hardware boxes where data goes in and comes out, just to make telcos happy, but everything else -I mean all the OS and apps- should be native and user accessible. This way one gets the best possible performance while maintaining a high degree of separation between kernel+userland and radio chipset which would let allow hacking whilst preventing anyone to tamper with cell connectivity.