#libcurl grew with a mere 100 lines of code in 2025. At 149,000 lines.
When you‘re low on RAM, I recommend using a recent #curl for your internet transfers.
It can shuffle gigabytes back and forth using a few MB of your memory (mostly used by openssl).
If you develop an application, you can use #libcurl to gain its benefits.
Need to shape your traffic? For example bc you run a streaming service? #libcurl does that for you for all HTTP versions.
When you‘re low on RAM, I recommend using a recent #curl for your internet transfers.
It can shuffle gigabytes back and forth using a few MB of your memory (mostly used by openssl).
If you develop an application, you can use #libcurl to gain its benefits.
Need to shape your traffic? For example bc you run a streaming service? #libcurl does that for you for all HTTP versions.
If you have an idea for a <500 line stand-alone example C code using #libcurl, tell us!
#libcurl backends, the November 2025 update
On this day last year, #libcurl celebrated its 18th anniversary of not breaking the ABI.
That makes it 19 years now.
https://daniel.haxx.se/blog/2024/10/30/eighteen-years-of-abi-stability/
On this day last year, #libcurl celebrated its 18th anniversary of not breaking the ABI.
That makes it 19 years now.
https://daniel.haxx.se/blog/2024/10/30/eighteen-years-of-abi-stability/
Yesterday I requested a person to pay for support as they desperately asked me for immediate help with their #libcurl problem (for a huge international company doing an expensive commercial device), seemingly in a hurry.
To which the user said no thanks, closed the issue and vanished.
The open source life.