> This is the point where, in the before times, I’d push it up to GitHub. But why would I? You can build it yourself, with a UI that suits you.
Because the technology is neither free, nor instant, nor fully deterministic; and it will not and cannot ever be as inexpensive, fast or reproducible as a download. I cannot find a bug in your version and warn you about it (and certainly can't propose to fix it for you). If I get an idea and improve my own version, nobody else benefits from my insight.
Why would I expect the software to be useful if that prompt block represents the entire essential complexity of the code, which should be seen as enough information to reproduce the program?
Nothing fundamentally changes about the virtues of open-source simply because software is easier to create.
> I know some people will be thinking, come on man, you’ve done the hard part of building the app, just give it to us. But really, that’s not the hard part anymore. In fact, none of this was particularly difficult.
Okay, so thus far we've considered the developer's perspective. Let's also imagine a user's perspective:
There are a lot of things that someone might suggest in the prompt that would be counterproductive; and I see there's mention of a "gotcha" which indicates that the author must have tried something more naive and then realized that a correction would be needed. Not to mention, there's been an explicit attempt to design an API. I would wager that the large majority of people who might want an "app for browsing and bulk-deleting my Prime Video and Netflix watch history." have no idea what an API is, never mind what GET and POST methods are etc. That is, they would need the insight of a post like this to succeed in getting a reasonable result.
This kind of analysis is, in fact, the hard part, once the actual code writing is made easier.
> What would be difficult is supporting an open-source project that does this. It’s built on Prime’s undocumented API, so it will break. If I open-sourced it, I’d be signing up for a steady stream of “it’s stopped working” issues. There would also be the usual bunch of feature requests for things I don’t need. Open-source projects can quickly become a thankless task.
Again: OP did the research of an undocumented API, so what's described is out of reach of many end users anyway.
But if you don't want to take responsibility, you could just not. There's tons of stuff out there that's basically just abandoned; the world is still better for it having existed in the first place. Just offering a binary release and the appropriate license disclaimers is already putting end users way ahead of where they'd be otherwise.
> if building things is this easy now, why do these services have such terrible UIs for managing your watch history?
What incentive do they have to provide a better UI?
Why would we suppose that they've even considered that a problem exists?
Because the technology is neither free, nor instant, nor fully deterministic; and it will not and cannot ever be as inexpensive, fast or reproducible as a download. I cannot find a bug in your version and warn you about it (and certainly can't propose to fix it for you). If I get an idea and improve my own version, nobody else benefits from my insight.
Why would I expect the software to be useful if that prompt block represents the entire essential complexity of the code, which should be seen as enough information to reproduce the program?
Nothing fundamentally changes about the virtues of open-source simply because software is easier to create.
> I know some people will be thinking, come on man, you’ve done the hard part of building the app, just give it to us. But really, that’s not the hard part anymore. In fact, none of this was particularly difficult.
Okay, so thus far we've considered the developer's perspective. Let's also imagine a user's perspective:
There are a lot of things that someone might suggest in the prompt that would be counterproductive; and I see there's mention of a "gotcha" which indicates that the author must have tried something more naive and then realized that a correction would be needed. Not to mention, there's been an explicit attempt to design an API. I would wager that the large majority of people who might want an "app for browsing and bulk-deleting my Prime Video and Netflix watch history." have no idea what an API is, never mind what GET and POST methods are etc. That is, they would need the insight of a post like this to succeed in getting a reasonable result.
This kind of analysis is, in fact, the hard part, once the actual code writing is made easier.
> What would be difficult is supporting an open-source project that does this. It’s built on Prime’s undocumented API, so it will break. If I open-sourced it, I’d be signing up for a steady stream of “it’s stopped working” issues. There would also be the usual bunch of feature requests for things I don’t need. Open-source projects can quickly become a thankless task.
Again: OP did the research of an undocumented API, so what's described is out of reach of many end users anyway.
But if you don't want to take responsibility, you could just not. There's tons of stuff out there that's basically just abandoned; the world is still better for it having existed in the first place. Just offering a binary release and the appropriate license disclaimers is already putting end users way ahead of where they'd be otherwise.
> if building things is this easy now, why do these services have such terrible UIs for managing your watch history?
What incentive do they have to provide a better UI?
Why would we suppose that they've even considered that a problem exists?
reply