Skip to content

Survey: curl and libcurl 2015

Viktor Szakats edited this page Apr 20, 2015 · 12 revisions

curl survey

The results from 2014

The plan is to make another curl survey, to make it annual. This is the planned questions for the 2015 version:

How are you using curl/libcurl?

  1. Please check the protocols you use curl/libcurl for (multi select)
  2. Do you use curl/libcurl on multiple platforms?
  3. How many years have you been using libcurl?
  4. Are you subscribed to a curl mailing list?
  5. Tell us which features you use? (NEW 2015)
  • HTTP automatic decompression
  • Bandwidth limiting
  • HTTP proxy
  • SOCKS proxy
  • HTTP/2
  • .netrc
  • using libcurl multi-threaded
  • TCP keepalive
  • SSL/TLS client certificates
  • UNIX sockets
  • the share interface
  1. Which SSL backends do you use? (NEW 2015)
  2. If you're using a binding, tell us which! (NEW 2015)

What kind of person are you?

  1. How have you contributed to the curl project?
  • I've filed bug report(s)
  • I've sent patch(es)
  • I've responded to questions on mailing list / forums
  • I've helped out in other ways
  • I run tests or provide infrastructure
  1. Are you involved in other open source projects?
  2. What are the primary reasons you haven't contributed or don't contribute more to the project?
  • everything works to my satisfaction
  • things get fixed fast enough anyway
  • the project doesn't want my changes
  • I don't have the time
  • I don't have the energy
  • I don't know the programming languages used
  • I find it hard to work with the curl developers
  • I can't deal with the tools (git, make, diff etc)
  • I don't like or use email
  • my work/legal reasons prohibit me
  • Other:
  1. How good is the project and its members to handle... (rate 1-5)
  • patches
  • bug reports
  • female contributors and other minorities
  • attribution and giving credits
  • helping newcomers to the project

Pick the best and worst

  1. Which are the curl project's best areas (pick at most 5)
  • transfer speeds
  • the support of many protocols
  • the quality of the products, curl/libcurl
  • the features of the protocol implementations
  • bug fix rate
  • documentation
  • the user and developer community
  • project leadership
  • its build environment/setup
  • project web site and infrastructure
  • support of multiple SSL backends
  • test suite
  • its availability and functionality on many platforms
  • welcoming to new users and contributors
  • footprint of the library/executable
  • standards compliance
  • the libcurl API
  1. Which are the curl project's worst areas (pick at most 5)
  • same areas as for the best area

Competition

  1. If you couldn't use libcurl, what would be your preferred alternative?
  • wget (or code ripped out from wget)
  • libsoup
  • native lib in Perl, Python, Java, etc
  • Windows native libs (wininet or the likes)
  • homegrown
  • neon
  • serf
  • Other:

Future

  1. If you miss support for any protocol, tell us which!
  2. What feature/bug fix would you like to see the project implement next?
  3. What feature/bug fix would you like to see the project REMOVE? (NEW 2015)
  4. What of these API(s) would you use if they were added? (NEW 2015)
  • URI handling (parsing/splitting)
  • setting up multithreaded mutexes in an agnostic way
  • handling of TLS certs/keys in memory