"Let's move application development to Python then, I suppose."
"Thanks, that fixed it."
Probably what happened in my 55" smart TV dev team.
What's worse, they made a "throbber" effect by string substituting a different color into an SVG, and then reparsing the SVG, for each color it fades through.
That's the kind of coding quality the OLPC project had. That's why it failed, and it probably also factored into why they disabled the view source button.
Typical dev time for a new UI from scratch is years. And price drop on parts and their availability will be different down the road.
I wonder of people are running all tests, DEV work in KVM or other emulation stacks for DEV, but then not accurately locking clock rate, and limiting RAM during testing.
Because I'd quit as a DEV, if I saw the fruits of my labours, turning out as complete crap and a laughing stock. I wouldn't want my name associated with laggy, crashy, frustrating junk. I'd want no part of it, no part of everyone hating my work.
And further, how the hell does laggy crap get past the CTO? CEO? I've seen lag just trying to change the channel!
I mean, outside of caring about customers every buying anything with your name again, there's the laughing stock factor.
"Hi, I'm CEO of crappy corp"
"Wow, you must be really proud of yourself, dumbass"
I just don't get it. CEO bonuses aside, saving 10 cents on a part, over 10M units is still only $1M extra profit, and the CEO might see a tiny fraction, as a bonus, of that extra profit.
I don't grok.
The problem is, there is no competition, everyone sucks and only builds to "it works somewhat" quality. Hence, no incentive for anyone to invest more money.