5 ms·

Anything to satisfy whichever law it is that says "lagginess remains constant".

• actionfromafar 3y ago
  "Huh, this CPU is kind of snappy running native code now. What should we do?" "Let's move application development to Python then, I suppose." "Thanks, that fixed it." Probably what happened in my 55" smart TV dev team.
  • xnzakg 3y ago
    I would bet that instead of python it's JavaScript and a webapp pretending to be a native application.
    • treyd 3y ago
      If it's an LG TV this is literally true. They bought webOS specifically for this purpose. Meanwhile Roku invented a runtime/language (BrightScript) and mandated its use to at least enforce a minimum quality standard and throw away cruft.
      • pjmlp 3y ago
        WebOS supports Qt as well.
  • bitwize 3y ago
    Definitely happened on the OLPC. 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.
    • adhesive_wombat 3y ago
      In modern GTK you also have to string-substitute or otherwise construct CSS, pass in as a string and have it reparsed to change element styles. But at least it is native!
    • actionfromafar 3y ago
      It also failed because it took ages to release anything useful. It took years, and suddenly smartphones were upon us all, and OLPC shrunk from a special niche to a tiny niche.