Re:API design: Which version of versioning is right for you?
by wellpast on Monday October 07, 2019 @10:12PM
(#21188003)
See the link to Rich Hickey’s talk in my other comment. It covers the issues pretty well.
I’m not being contrarian, but I am expressing frustration with a common yet unnecessarily complicated approach to a general problem. But I stand by my statements, they’ve paid off tremendously in real world contexts.
Because the API may serve the same purpose as the original, with some modified semantics.
> Also, why is it versioning?
Because the API may serve the same purpose as the original, with some modified semantics.
Sharing a common name with versioning helps identify the relationships between the versions. It also avoids polluting the API namespace with a set of different names for different versions of essentially the same operations.
> Thinking in “versions” is not an accurate/ergonomic mapping of the domain anyway; we’ve just been tricked into thinking that way because... anthropology something.
It feels to me like you're trying to hard to be contrarian, or perhaps you're dealing with some special case scenario where your strategy makes sense.
You'd need to explain the argument in significantly more detail to have a chance of making it convincing.