3 ms·
Migrating to better APIs is done all the time. It is not an issue worth discussing about anymore. But even if you have to maintain an API this doesn't mean you
by coliveira 3y ago
Migrating to better APIs is done all the time. It is not an issue worth discussing about anymore. But even if you have to maintain an API this doesn't mean you cannot change the underlying implementation.
- simonw 3y agoIt absolutely is an issue worth discussing, any time you are maintaining a library with more than a few other people using it. Breaking backwards compatibility in a library with hundreds or thousands of users is not something to be taken lightly!
- wvenable 3y agoI'm working with an API right now that is absolutely based on duplicated code. They have a system for querying items and the API has 3 different ways depending on the endpoint. I just found a new one the other day and I hated it -- why is this one API unnecessarily different from all the rest! I'm building a library to call this API and I've abstracted over all these differences so my callers never have to know how messed up the underlying API is -- they get a consistent experience regardless.