There's also the unspoken third one which is off by one errors.

Like they said, the two hard problems.

ISWYDT

Obiwan errors are greatly reduced in more modern language that have newer mechanisms for looping over data.

And the fourth: scope creep.

This isn't really a naming problem, though, although the naming is poor. Better naming or more clarity isn't going to fix the fundamental problem - Apple TV doesn't deliver on the promise of an (idealized) Apple product/service.

A good Apple product may in some ways be more constrained than similar products but is easy to understand and use and 'just works'. For instance, you bought an iPod and you plugged it into your Mac which popped up a store where you could buy music. You didn't have to know what an 'mp3' is. Or you bought an iPhone, took it home, plugged into your computer and 3 minutes later had a working new phone/pocket web browser. You didn't have to listen to anyone telling you about extended warranty and the web browser actually worked.

Buying an Apple TV or subscribing to the service doesn't solve any of the endless irritations and inconveniences associated with consuming TV or movies online. It just names them all Apple TV but if they fixed that, the irritations and inconveniences would still be there.

But they can both be solved by adding another layer of indirection.

You're thinking of Haskell. Apparently it solves all the problems.

Fools, Electron is the One True Messiah.

It solves all problems by leaving no memory and battery for them to happen in.