News for hackers. Stuff that matters.
Re:How to Version an API by smizell on Thursday June 08, 2017 @04:35PM (#14516996)
That's true. However, I think this falls under YAGNI [0]. If you happen to get to a point where you have to change your an entire API rather than evolve what you have, you should consider it a new, separate API rather than instruct all client developers to plan for it up front. Plan for evolvability and handling changing requirements up front.

[0] https://martinfowler.com/bliki/Yagni.html

Re:How to Version an API by ljcrabs on Friday June 09, 2017 @02:02AM (#14519445)
And how would you name this new API? Bob? Or version 2?
Re:How to Version an API by smizell on Friday June 09, 2017 @09:53AM (#14521350)
Name it whatever you want. Point is, you don't have to plan for such a drastic change when a separate domain/subdomain will solve it for you.