Hello everyone!
The Haskell Foundation is reviving @taylorfausak’s State of Haskell Survey. It’s been a few years and so we’re doing it a bit differently, but the plan is to start doing this yearly again so that we can collect longitudinal data on the Haskell community and ecosystem.
Please take the ~10 minutes to fill this out and share it with friends/colleagues/coworkers, whether or not they are users of Haskell.
Thanks!
-Jose
Answered! Thanks a lot
Filled out mine and submitted!
Thanks for doing this! I’ve sent mine. Cheers
I asked some non-Haskell colleagues, as directed, (a combination of data science people and software engineers - some who have tried Haskell others who haven’t) to do the survey and after the first page there were a lot of Haskell specific questions they couldn’t answer e.g I’m satisfied with stack or hackage.
Idk how these surveys are setup it might be good to have early exit after the generic part of the survey. Cause it was a little hard to get them to complete it.
Thanks for pointing that out.
I had intended to have folks that clicked “no, and I never have” to skip most of the Survey (the stuff that requires Haskell knowledge). It is now fixed (it only skipped some, not sure what happened).
There were also quite a few questions you were forced to fill out despite your previous answers, such as “how long did you use Haskell for before giving up” (sorry I don’t have the exact wording in front of me) despite answering “I still actively use Haskell” in a previous question. I worry that forcing people to answer such questions is going to lead to a fair chunk of junk answers, so you’ll need to be careful in your analysis of the results.
I didn’t encounter any required questions when I took the survey. I just skipped some that I didn’t feel were applicable.
I would have liked there to be an option to write why people that stopped using haskell, stopped doing so
Likewise. We (a two-person research team) stopped using Haskell because all the cryptography and zero-knowledge proof libraries we wanted to use are written in Rust. Initially we did FFI to those libraries, but it became too much of a PITA, so we just switched to Rust ourselves.