While the author doesn't seem to like version based APIs very much, I always recommend baking them in from the very start of your application.
You cannot predict the future and chances are there will be some breaking change forced upon you by someone or something out of your control.
xtacy · 33m ago
Are there good public examples of well designed APIs that have stood the test of time?
binaryturtle · 7m ago
I always thought the Amiga APIs with the tag lists were cool. You easily could extend the API/ABI w/o breaking anything at the binary level (assuming you made the calls accept tag lists as parameters to begin with, of course).
cyberax · 56m ago
> You should let people use your APIs with a long-lived API key.
Sigh... I wish this were not true. It's a shame that no alternatives have emerged so far.
TrueDuality · 3m ago
There are other options that allow long-lived access with naturally rotating keys without OAuth and only a tiny amount of complexity increase that can be managed by a bash script. The refresh token/bearer token combo is pretty powerful and has MUCH stronger security properties than a bare API key.
You cannot predict the future and chances are there will be some breaking change forced upon you by someone or something out of your control.
Sigh... I wish this were not true. It's a shame that no alternatives have emerged so far.