Both Facebook and Netflix implemented their eponymous apps with Web. Despite spending millions of dollars, neither of them could achieve an iPhone-like user experience (60 frames per second and less than 100ms response to user inputs) on anything less powerful than a system-on-chip (SoC) with four ARM Cortex-A9 cores.
In contrast, numerous products like infotainment systems, in-flight entertainment systems, harvester terminals and home appliances prove that you can achieve an iPhone-like user experience (UX) on single-core Cortex-A8 SoCs. Our above-mentioned manufacturer HAM Inc. (renamed for the sake of confidentiality) verified these results by building both a Web and Qt prototype.
In this white paper, Burkhard Stubert explains how he could save one of the world's largest home appliance manufacturers millions of Euros by choosing Qt over HTML. The secret? Qt scales down to lower-end hardware a lot better, without sacrificing user experience.
With a five times smaller footprint, four to eight times lower RAM requirements and a more efficient rendering flow than HTML, Qt provides faster start-up times and maintains the cherished 60fps and 100ms response time, where HTML would struggle. The calculations show that being able to just downgrade your SoC by just one tier like this, Qt can reduce your hardware costs by over 53%.
(Score: 2) by Wootery on Friday February 23 2018, @06:44PM
This isn't inherent to Java, it's an issue with the way current JVMs typically work. There are two possible solutions:
1. Use Nailgun, [github.com] which essentially turns your command-line invocations into fast operations in an already-warm, long-lived JVM
2. Use a JVM with AOT compilation. Excelsior JET can already do this, and it may soon be coming to HotSpot.
.Net has a JIT cache, and fast start-up. .Net isn't like your average JVM - there's no mixed-mode execution with an interpreter.