4 ms·
I know you're getting a lot of pushback here, but you're totally right. Qt (among others) has been a thing in the embedded space for decades, and we've had snap
by switchbak 4y ago
I know you're getting a lot of pushback here, but you're totally right.
Qt (among others) has been a thing in the embedded space for decades, and we've had snappy UIs on sub gigahertz CPUs for decades. I just don't buy that's it's a matter of under specced hardware.
I'd actually buy that it's more a matter of the corporate sausage making machine that turns ok hardware and talented developers with good intentions into an output of barely usable poorly performing crap. Ie: exactly how we end up with something like Spotify.
- hikawaii 4y agoThe corporate sausage making machine is merely only doing what it's customers want, for the price they'll pay, nothing more, nothing less. A lot of these are good impulses but also feel like an unfunded mandate, like rear back up cameras being mandatory - obligating everyone pay a thousand dollars more every year. The feel good comes from the DOT, the cost gets paid by the customer.
- pySSK 4y ago> I'd actually buy that it's more a matter of the corporate sausage making machine This. The devs don't have a say in the tech stack. The decsion is usually outsourced to the lowest bidder. Other than Tesla and Rivian, I can't think of any OEMs that I've dealt with who have full control over control over their display. Almost everyone outsources it to the Koreans who have a lock on that market – i.e. OEMs send in their designs but it's actually implemented by LG, Samsung etc. From what I've seen, any changes or new additions to any on-screen components has a 2 year lead-time unless (not a typo) it's safety critical or catastrophic in some other way.