In software: "if it exists, there will be prod of it"
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Dumb/honest question: what exactly makes it not appropriate to prod?
-
The responses to
@li_haoyi's original tweet mention some reasons, but in summary, the API doesn't make it so easy to write reliable, bug-free code. (But instead, it makes it very easy to download a URL into a string.)
End of conversation
New conversation -
-
-
I'll stick with sttp ;) It's (almost?) as easy to use in a REPL/hacky script: https://github.com/softwaremill/sttp#quickstart-with-ammonite …, but it can also be used in production using the same API. Hacky script vs production-use doesn't have to be an alternative.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Spoiler: people are going to use it for production apps.
-
You are certainly not wrong...
- Show replies
New conversation -
-
-
I honestly don't understand why production and hacky-script has to have different libraries or interfaces. Python programmers have been using Python's requests everywhere and you don't hear them complain about it.
-
Being production-ready implies a certain degree of resilience against a variety of errors, security attacks and maintenance. Stringly-typed APIs mean you're not forced to handle certain errors, you're at risk of injection attacks, and your app is likely to break when APIs change.
End of conversation
New conversation -
-
-
It seemed to me that the criticism was of the comparison between http4s and request-scala rather than a criticism of request-scala itself. IMHO, the criticism was just.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Wasn't the same goal shared with http://unirest.io/java.html ?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.