Yeah I should probably take that option more seriously myself – I tend to be happiest writing my own HTTP request calling logic, but if they satisfy developers who prefer a library I should spend time properly figuring them out
@simonw
-
AWS reliability advantage: 15-year track record stability matters
By
–
That's one of AWS's biggest advantages in my mind – they have about a 15 year track record of not breaking stuff Anyone else who wants to build up that kind of track record needs to spend 15 years doing it
-
AWS Reliability and Product Trust in Cloud Computing
By
–
Yeah that's true, AWS are uncommonly good at keeping their stuff working – not just boto3 but all of their AWS products in general I don't trust anyone else though!
-
Clean API Design: HTTP Libraries and Documentation Best Practices
By
–
Maybe the solution to that conundrum is to design your API to be as clean to access from good language HTTP libraries (like httpx) as possible, then include copy-and-paste examples in your documentation that are clear enough that the desire for a client library doesn't emerge
-
API Providers Must Ship Client Libraries for Control
By
–
On a related strategic note though: API providers do need to ship client libraries, because if you don't someone else will – and then you could end up in a situation where lots of people are using a client library that you can't release new versions of when you have API updates
-
Python Library Complexity for Direct HTTP Calls to Gemini
By
–
I know Python really well and I still don't like to have to reverse engineer their Python libraries to figure out how to make a direct HTTP call! I had to do that for Gemini just last week
-
Testing LLM Clients: httpx and pytest-httpx Best Practices
By
–
Plus I like to write tests for my code, and figuring out how to serve a mock HTTP response to each different LLM client library in turn is a whole lot more work than just using httpx and pytest-httpx – which I already know
-
Testing LLM Client Libraries with httpx and pytest-httpx
By
–
Plus I like to write tests for my code, and figuring out how to serve a mock HTTP response to each different LLM client library in turn is a whole lot more work than just using httpx and pytest-httpx – which I already know
-
Client Libraries Breaking Changes: Trust Issues in API Wrappers
By
–
… which is a bit unintuitive because one would expect that part of the promise of client libraries would be insulating their users from breaking changes made to the JSON APIs that they wrap I have been burned enough times now: I don't trust vendor client libraries not to break
-
API Documentation: JSON Specs Over Client Libraries
By
–
Request for model API providers: please put JSON API docs (with example curl commands) somewhere prominent I always look for those first, before client libraries, because my experience is that client libraries are more likely to have backwards incompatible breaking changes