|
|
|
|
|
|
by KingMachiavelli
1164 days ago
|
|
|
Because 8 bit hardware was realtime? It's quite difficult to implement everything we expect likely nowadays without multiprocessing... realtime Linux exists but it's not a panacea Honestly to compete with mass market TVs, it's going to be difficult to avoid have more- not less "bloat". Built-in Android would be a great selling point (saves you $200 on a NVidia Shield as long as it doesn't track you or lock down features). Built-in AI upscaling is a good selling point. I would also think if you have a OLED or edge/direct LED backlight LCD then you also need to run much more complicated pixel/zone brightness algorithms.... There's probable more memory allocated per frame on a modern 4K TV than an 8-bit computer had in total. |
|
|
No, the reason that UIs are slow are because they are often a web browser, running a Javascript bloatware UI with it's shadow DOM or whatever, and there's a heaps of bullshit going on before anything happens on screen at all.
And this is fine! For many use-cases, comparatively beefy PCs, web pages etc.
But for what is effectively an embedded product which will get updated seldom if ever, THIS is the time to take a step and rethink what you are doing.
For a non-smart TV you definitely don't need Linux, (but you could!) and you don't need to care if it's realtime or not. There should be only one or two processes running anyway, so there shouldn't be any competition between different threads. It's should all be coded like a classic, tight game-loop.
AI upscaling and Android... dear lord. Just give me something which isn't fucking slow and frustrating to use. I thought I was in the thread which discussed non-smart TVs, did I miss something?