Curlese, Five Years Later
hypertesto.me
Curlese, Five Years Later
1–8 of 8 posts
Re: Curlese, Five Years Later
#2Curlese, five years later: curl is still the universal language of broken integrations
Re: Curlese, Five Years Later
#3Author here, thanks for posting this, I didn't expect to see traffic coming from HN.
I wrote the original "curlese" post (in Italian) back in 2021: the idea that when an HTTP integration breaks, a `curl -v` command is the only language every team should speak. Curl is the ideal tool since you don't have to share logs and neither prove your application behaviour. The thesis stood the test of time :-)
Re: Curlese, Five Years Later
#4Author here, thanks for posting this, I didn't expect to see traffic coming from HN. I wrote the original "curlese" post (in Italian) back in 2021: the idea that when an HTTP integration breaks, a `curl -v` command is the only language every team should speak. Curl is the ideal tool since you don't have to share logs and neither prove your application behaviour. The thesis stood the test of time :-)
You should probably link to the previous post, it’s a right pain to find.
Also is there an approved English version of it, or the same information by someone else?
edit: as pointed out there is one (to an english translation) in the first footnote
Re: Curlese, Five Years Later
#5Author here, thanks for posting this, I didn't expect to see traffic coming from HN. I wrote the original "curlese" post (in Italian) back in 2021: the idea that when an HTTP integration breaks, a `curl -v` command is the only language every team should speak. Curl is the ideal tool since you don't have to share logs and neither prove your application behaviour. The thesis stood the test of time :-)
You should probably link to the previous post, it’s a right pain to find. Also is there an approved English version of it, or the same information by someone else? edit: as pointed out there is one (to an english translation) in the first footnote
There seems to be a link to an English translation in footnote 1 of this article
Re: Curlese, Five Years Later
#6Earlier quoted context omitted.
You should probably link to the previous post, it’s a right pain to find. Also is there an approved English version of it, or the same information by someone else? edit: as pointed out there is one (to an english translation) in the first footnote
There seems to be a link to an English translation in footnote 1 of this article
So there is, thank you for the directions.
Re: Curlese, Five Years Later
#7Author here, thanks for posting this, I didn't expect to see traffic coming from HN. I wrote the original "curlese" post (in Italian) back in 2021: the idea that when an HTTP integration breaks, a `curl -v` command is the only language every team should speak. Curl is the ideal tool since you don't have to share logs and neither prove your application behaviour. The thesis stood the test of time :-)
You should probably link to the previous post, it’s a right pain to find. Also is there an approved English version of it, or the same information by someone else? edit: as pointed out there is one (to an english translation) in the first footnote
The english version of the 2021 post was not intended when I wrote this post.
I've had a kind contribution for it directly on the repository, I will update the links in the article to make it easier to find!
Thanks for reading!
Re: Curlese, Five Years Later
#8Earlier quoted context omitted.
You should probably link to the previous post, it’s a right pain to find. Also is there an approved English version of it, or the same information by someone else? edit: as pointed out there is one (to an english translation) in the first footnote
The english version of the 2021 post was not intended when I wrote this post. I've had a kind contribution for it directly on the repository, I will update the links in the article to make it easier to find! Thanks for reading!
Thanks for writing!
An other commenter pointed me towards the link in the first footnote. May I suggest linking most of the opening sentence, from "a post" to "curlese"? That would make it very clear where said previous post is.
Also maybe cross-link the italian and contributed english versions of the original post in case someone else finds the former and can't read italian, the contributed translation is definitely quite a bit better than Apple's automated translation at the very least.