5 ms·

That's the problem, the company didn't publicly engage with their users that needed it. A simple intent to ship with a list of changes related to API's is a gre

That's the problem, the company didn't publicly engage with their users that needed it. A simple intent to ship with a list of changes related to API's is a great start. The employees should be using the most popular of the user made software. That's how organic communities function. The problems occur when company thinks theyre God and their software is controllable - it's not. People are going to use it as they see fit, and if you don't Shepard it that community will find their owns reasons for why the company ignores it.

wdb 5y ago
There is typically a reason when APIs are not documented. There are no guarantees given it will keep working etc
- devwastaken 5y ago
  Many times undocumented API's become a lot more permanent and 3rd party documented. If you don't do it, other people will, it's better to handle that problem from the company itself and put bit fat "can break any time" stickers on it.
parineum 5y ago
>A simple intent to ship with a list of changes related to API's is a great start. So the controversy can start sooner? >The problems occur when company thinks theyre God and their software is controllable - it's not. This isn't some github project. This is proprietary software owned by Netflix. This isn't "the community" getting upset, this is a small group of people using closed source software in a way that wasn't intended. Most people using Netflix just use it the way Netflix wants them to.
- devwastaken 5y ago
  You would be apart of the problem, not the solution. Attitudes like that are exactly how that happens.
  - parineum 5y ago
    I am for open standards and accessible apis and support companies that provide those things. Netflix neither promised or delivered those things and it's extra work to maintain them. They don't owe anyone to maintain backwards compatibility on the undocumented public facing apis. It's unreasonable to expect Netflix to deliver a feature that they have no interest in providing and never promised to. I use a lot of software that relies on apis like that and it breaks constantly, that's just the way it goes.

wdb 5y ago

There is typically a reason when APIs are not documented. There are no guarantees given it will keep working etc

devwastaken 5y ago
Many times undocumented API's become a lot more permanent and 3rd party documented. If you don't do it, other people will, it's better to handle that problem from the company itself and put bit fat "can break any time" stickers on it.

parineum 5y ago

>A simple intent to ship with a list of changes related to API's is a great start. So the controversy can start sooner? >The problems occur when company thinks theyre God and their software is controllable - it's not. This isn't some github project. This is proprietary software owned by Netflix. This isn't "the community" getting upset, this is a small group of people using closed source software in a way that wasn't intended. Most people using Netflix just use it the way Netflix wants them to.

devwastaken 5y ago
You would be apart of the problem, not the solution. Attitudes like that are exactly how that happens.
- parineum 5y ago
  I am for open standards and accessible apis and support companies that provide those things. Netflix neither promised or delivered those things and it's extra work to maintain them. They don't owe anyone to maintain backwards compatibility on the undocumented public facing apis. It's unreasonable to expect Netflix to deliver a feature that they have no interest in providing and never promised to. I use a lot of software that relies on apis like that and it breaks constantly, that's just the way it goes.