4 ms·
Sure. Those are conveniences. However, most of the Getting Started articles that you find about any publicly published REST API usually starts you off with a b
by addicted 9y ago
Sure. Those are conveniences.
However, most of the Getting Started articles that you find about any publicly published REST API usually starts you off with a bunch of curl commands.
Even if the networking aspects are completely hidden from you in your application, your formative experiences with the REST API almost certainly was with the network requests.
- speedplane 9y agoGiven the dozens of languages and libraries that interact with APIs, I don't see the issue of starting with a curl command. It's a common denominator, programmers of almost all languages understand, like international sign language. No one would seriously use curl commands in production, but load up a command window, and it's an easy way to start messing around. Agree with your second point though... network requests are hard. They are not much different from real distributed programming. Making REST requests should be done with care.
- empath75 9y agoI do use curl commands in production for stuff like user data in an aws cloudformation template. Having an api I can hit with curl that returns json I can parse with jq is super convenient.
- matt_kantor 9y agoI don't think the parent commenter sees curl-centric getting started guides as an issue either. Actually from this thread's context I assumed they thought it was a good thing.