* examining the docs
* taking care of error handling
* coming up with an easy to use developer interface
* keeping it updated if the API calls were to change
every time you need translation.
You're also implying it's better than having a package that can potentially abstract many different translations API, that you can just add as a submodule of your git repository, and use with one `require()` call away.
I disagree.