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: 5, Funny) by The Mighty Buzzard on Friday February 23 2018, @01:31AM (11 children)
That headline's like asking if you'd prefer to be kicked in the left testicle or the right.
My rights don't end where your fear begins.
(Score: 4, Informative) by fyngyrz on Friday February 23 2018, @01:38AM
Speaking as a pretty in-depth QT developer - hundreds of thousands of lines of c++ / QT class based code - I enthusiastically second your opinion.
Also, once they move on and leave your version of QT unsupported, you get to be kicked in both. For no good reason at all except "drool, new, shiny" on the part of the QT devs themselves. Idiots.
QT's cross-platform capability is great - until you run into bugs, and/or until they leave you behind. Then things get... interesting.
(Score: 4, Funny) by driverless on Friday February 23 2018, @03:32AM
Kick away, we're a Unix shop here.
(Score: 2) by FatPhil on Friday February 23 2018, @04:47AM (3 children)
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
(Score: 3, Insightful) by The Mighty Buzzard on Friday February 23 2018, @06:07AM (2 children)
The left. It's the sinister one. After time to think it over though, I'd almost always rather get kicked in the crotch than do any sort of GUI coding beyond what I do on the site here; the pain doesn't last nearly as long. Give me a nice, simple shared library, a CLI utility, or even something running on some microcontroller's bare metal any day of the week.
My rights don't end where your fear begins.
(Score: 3, Touché) by chromas on Friday February 23 2018, @08:16AM (1 child)
Won't kicking that testicle make it the regressive left?
(Score: 0) by Anonymous Coward on Friday February 23 2018, @03:49PM
Is that why y'all conservatives are always so ornery? Your right testicles have been caved in? Might explain the obsession with "vucking" as your nuts can't fire live rounds?
(Score: 2) by Pino P on Friday February 23 2018, @07:22PM (3 children)
Which free software GUI framework that does not involve testicular assault would you prefer to these two?
(Score: 2) by The Mighty Buzzard on Saturday February 24 2018, @12:16AM (2 children)
I wouldn't. I'm smart enough to not try running idiotic GUI bullshit on a microcontroller.
My rights don't end where your fear begins.
(Score: 2) by Pino P on Wednesday March 14 2018, @04:01PM (1 child)
Even if the configuration GUI runs on a device-that-is-not-a-microcontroller and sends the finished configuration to the microcontroller, you still need a framework for the configuration GUI that runs on a device-that-is-not-a-microcontroller, whether said device-that-is-not-a-microcontroller runs Windows 7, Windows 10 in S mode, GNU/Linux, Android, macOS, or iOS. Which GUI framework for an app that runs on a device-that-is-not-a-microcontroller is preferred?
(Score: 2) by The Mighty Buzzard on Wednesday March 14 2018, @04:43PM
In that specific instance? HTML. Either internet or local network accessible depending on your specific needs but it makes zero sense to allow multiple devices to have configuration change permissions when it can be done more easily and securely from a centralized source. Ideally the devices to be configured wouldn't even accept incoming traffic at all but would instead poll a server at regular intervals; admittedly this is not always viable.
My rights don't end where your fear begins.
(Score: 2) by Wootery on Friday February 23 2018, @07:45PM
Well, one is ugly, hairy and bloated, and the other is surprisingly elegant.