Enhance Why in README about katipo HOT 5 CLOSED

@lc3t35 the main reason we chose libcurl is that every bug we found in existing Erlang HTTP clients (we used 4 in our project) didn't exist in libcurl. That's the compatibility the readme talks about. Check the number of commits curl has - 19766! That's a lot of eyes. Does that help?

from katipo.

Sorry imho it does not help, please would you mind sharing/listing the bugs you found in existing clients (which bug affects which clients) ? In your case you seem to know very well libcurl, perfect but maybe the community is not and would prefer to fix bugs in existing clients, did you submit an issue in each client repo ? It might be also interesting to let users of these clients know the limitations (or bugs) so they can choose another client or katipo ;) Thank you.

from katipo.

Sure we submitted both issues and PRs for problems we came across. I don't think it's worth putting them in our readme however.

The community is fixing bugs and improving existing clients. The line Katipo takes is that they're not doing so at the rate libcurl is.

As for client limitations, these will depend highly on how they're being used. I really couldn't make any blanket statement on which to use.

from katipo.

I agree not to put that in Readme, but it might have some interest here in this issue: if you can please just provide the links to issues. With this crosspost, you'll get more visits to katipo as a good solution to fix the problem.

from katipo.

I think the readme is clear enough and there's nothing to be gained by posting issues in other clients. Closing this for now. If you have any changes to the code feel free to send a pull request.

from katipo.