That's a bad reason.
There's a solidly developed C library for dealing with HTTP, which is mature.
libcurl.
HTTP is developing, with WebSockets and the rest of the 2 spec.
C developers didn't immediately ditch what they use and fragment the ecosystem.
Curl got updated.
Python has a mature library, which is much younger than curl, called requests.
Python didn't fragment, they updated requests.
Here's where I have the biggest issue:
* Advice for C on which library to use, is probably still up to date 10 years later.
* Advice for Python on which library to use, is probably still up to date 5 years later.
* Advice for JavaScript on which library to use, is probably out of date 1 year later.
That's a bad reason.
There's a solidly developed C library for dealing with HTTP, which is mature.
libcurl.
HTTP is developing, with WebSockets and the rest of the 2 spec.
C developers didn't immediately ditch what they use and fragment the ecosystem.
Curl got updated.
Python has a mature library, which is much younger than curl, called requests.
Python didn't fragment, they updated requests.
Here's where I have the biggest issue:
* Advice for C on which library to use, is probably still up to date 10 years later.
* Advice for Python on which library to use, is probably still up to date 5 years later.
* Advice for JavaScript on which library to use, is probably out of date 1 year later.