← Back to context

Comment by dist-epoch

14 hours ago

> I have been working full-time on curl since 2019. For me, this typically means doing 50 hour work weeks, as I spend all days on it and then I top them off with a few more hours every late night – all days of the week

I wonder what is there to work on curl 50 hour weeks for 7 years?

https://curl.se/libcurl/

Let me Google that for you.

supporting DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, MQTTS, POP3, POP3S, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS. libcurl supports SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form based upload, proxies, HTTP/2, HTTP/3, cookies, user+password authentication (Basic, Digest, NTLM, Negotiate, Kerberos), file transfer resume, http proxy tunneling and more!

libcurl is highly portable, it builds and works identically on numerous platforms, including Solaris, NetBSD, FreeBSD, OpenBSD, Darwin, HPUX, IRIX, AIX, Tru64, Linux, UnixWare, HURD, Windows, Amiga, OS/2, BeOs, macOS, Ultrix, QNX, OpenVMS, RISC OS, Novell NetWare, DOS and more...

This is the HTTP/1.1 standard: https://datatracker.ietf.org/doc/html/rfc2616

Then there are also HTTP/2 and HTTP/3.

That's just HTTP, curl supports 27 other protocols.

  • HTTP/1.1 - June 1999

    It's not like the standard changed since curl was created

    • It (the http rfc) refers to other standards such as for URLs, and those did actually change (to include ipv6 and more internationalisation).

When we are talking about one of the most used pieces of software in the world, there is always things to do.

What do you work on? My guess is you have an inexhaustible list of work to be done, right? We all do, curl included.