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 driverless on Saturday February 24 2018, @02:16AM (1 child)
The really crazy thing about this is that while the initial argument was "code once, run anywhere", what they ended up with was "code once, run on Windows 7 or 8". I don't think that stuff has ever been run on anything else (well, used to run on XP and Vista when it was supported).
(Score: 2) by JoeMerchant on Saturday February 24 2018, @03:44AM
I've run Java on Linux and OS-X, but only with great pain - special attention to environment details, etc. Some of my least favorite technologies are the "Java based" cross platform ones: red5 media server and Mirth Connect are the two most recent, but it seems like every couple of years I encounter some giant steaming pile of Java that it's easier to just use for whatever thing it is I need to do quickly, but if I had to live with it as a customer facing (stable) solution, it would just about have to be recoded in something else.
🌻🌻 [google.com]