Why does every API need its own set of client libraries? Wasn't the promise of RESTful APIs to obviate the need for such?
Is it perhaps because basic JSON handling and POST/GET processing is still so miserable in most environments?
Is it perhaps because basic JSON handling and POST/GET processing is still so miserable in most environments?
There are other advantages, like automatic documentation, easier management of versioning, schema/type verification, ...
So you don't need to add "the need" after the word obviate.
You can just say "Wasn't the promise of RESTful APIs to obviate this?"
Otherwise what you are really saying is -> "Wasn't the promise of RESTful APIs to remove the need the need for such?"
I'm bearish on 3rd party SDKs for apis these days as most are fairly thin wrappers around apis that don't add much value but give you little to no control over how the actual http calls are being made.
And of course you don't need a custom library. Its just nicer to have one as it facilitates code completion and leverages the compiler you're using instead of some new validation tool.