Re:Ask HN: Why is Google not making a language that runs on ...
by rurban on Sunday July 15, 2018 @05:19AM
(#17534491)
This is not a language feature. We are talking about Dalvik here.
Low memory optimization means switching from a copying collector to a simple mark & sweep collector.
It's entirely up to the vendor to configure that JVM collector. Nokia does so I believe.
SW bloat in apps and bad config tunings for autocompletion and other user configs also lead to bad UI responses on low-powered phones.
Google is partially doing the right thing by providing all the frameworks by itself leading to reduced bloat. You just use the default library, in shared memory.
But a problem is of course Google removing the interpreter, costing a lot of discspace and memory.
Low memory optimization means switching from a copying collector to a simple mark & sweep collector. It's entirely up to the vendor to configure that JVM collector. Nokia does so I believe.
SW bloat in apps and bad config tunings for autocompletion and other user configs also lead to bad UI responses on low-powered phones. Google is partially doing the right thing by providing all the frameworks by itself leading to reduced bloat. You just use the default library, in shared memory. But a problem is of course Google removing the interpreter, costing a lot of discspace and memory.