2 ms·

For a TV, I don't see the problem with background apps dying. What does this mean? I wouldn't describe a streaming service, like Netflix, as a "background app"

by dfxm12 2y ago

For a TV, I don't see the problem with background apps dying. What does this mean? I wouldn't describe a streaming service, like Netflix, as a "background app" in the context of a HTPC/set top box. It's almost always a problem when devices, especially mono-purpose devices, slowly become bricks. No, browser can be fine, but I think it's harder to control in practice. Can you elaborate on this, too? If I don't like my browser anymore, I can switch browsers. Every browser I'm aware of has plug ins and and settings that give me control and the ability to extend functionality and to some extent, turn off some things I don't want. With apps, you're at the mercy of their developer. If the app sucks (or, again, gets killed off), you can do nothing but deal with it. I don't see what control one has there...

yjftsjthsd-h 2y ago
> What does this mean? I wouldn't describe a streaming service, like Netflix, as a "background app" in the context of a HTPC/set top box. It's almost always a problem when devices, especially mono-purpose devices, slowly become bricks. Oh, I thought you were talking about the OS killing background apps because these boxes don't have enough RAM. If you mean that it's a problem that services declare the system EOL and stop giving you access from it, then yes we agree. > Can you elaborate on this, too? If I don't like my browser anymore, I can switch browsers. Every browser I'm aware of has plug ins and and settings that give me control and the ability to extend functionality and to some extent, turn off some things I don't want. With apps, you're at the mercy of their developer. If the app sucks (or, again, gets killed off), you can do nothing but deal with it. I don't see what control one has there... Similarly talking past each other; I meant in a UX way. Yes, a browser is more flexible and gives you far more control, but native TV apps reliably work with nothing more than the buttons on a TV remote, which I don't trust web apps to do.

by dfxm12 2y ago

yjftsjthsd-h 2y ago

> What does this mean? I wouldn't describe a streaming service, like Netflix, as a "background app" in the context of a HTPC/set top box. It's almost always a problem when devices, especially mono-purpose devices, slowly become bricks. Oh, I thought you were talking about the OS killing background apps because these boxes don't have enough RAM. If you mean that it's a problem that services declare the system EOL and stop giving you access from it, then yes we agree. > Can you elaborate on this, too? If I don't like my browser anymore, I can switch browsers. Every browser I'm aware of has plug ins and and settings that give me control and the ability to extend functionality and to some extent, turn off some things I don't want. With apps, you're at the mercy of their developer. If the app sucks (or, again, gets killed off), you can do nothing but deal with it. I don't see what control one has there... Similarly talking past each other; I meant in a UX way. Yes, a browser is more flexible and gives you far more control, but native TV apps reliably work with nothing more than the buttons on a TV remote, which I don't trust web apps to do.