4 ms·
I wouldn't be surprised if the first comment is right that you could build a HTTP client sufficient for 90% of the usecases in ~100 lines or so. It's that other
by Denvercoder9 5y ago
I wouldn't be surprised if the first comment is right that you could build a HTTP client sufficient for 90% of the usecases in ~100 lines or so. It's that other 10% that takes 90% of the time, effort and complexity, and for which having libraries like curl is invaluable.
- bombcar 5y agoI think there are two classes of cURL users - those who use it as a "let me download this file to the current folder" users who always forget the -O; and that use case is quite simple and seems it could be easily replaced. And then there are those who use all the API features and realize it's a complex program. But the missing link is that even the first use case has many complex edge-cases that aren't obvious at first.
- swiley 5y agoI always use wget for the "let me download this file to the current folder" because I know the flags better. curl is for weird stuff like "POST" requests or other protocols.