[saulrh]

Consider an alternative reading:

50% of developers think they are as productive in a language they have four months of practice with as they are in a language they have fourteen years of practice with.

50% of developers think they are as productive in a high-performance bit-bashing-capable language as they are in a high-level glue language.

The people in this statistic are switching from languages they have years or sometimes decades of productivity in, and they're switching from languages like python and go and java. I see a lot of programmers who do similar switches never reaching productivity parity with C or C++. 50% of devs getting there in 4 months is amazing.

[PartiallyTyped]

I am willing to bet that the type system and the opinionated way of doing things helps a lot here.

Anecdata but I found myself very productive with Haskell when I was learning it for grad school, to the point where I knew that if it compiled, it was most likely right.

I had similar experiences though not to that degree with Rust with very little time spent on it in comparison to Haskell. I feel a lot more comfortable sleeping at night over C or Python.

[tasuki]

> Anecdata but I found myself very productive with Haskell when I was learning it for grad school, to the point where I knew that if it compiled, it was most likely right.

I recently told this to someone. The very next day my Elm code compiled just fine but it had three relatively tricky logical bugs which took me two hours to find and fix.

This was a rare enough occurrence that I remember it. Higher cosmic powers took note of my praise of strong typing and decided to teach me a lesson.

[PartiallyTyped]

Those are always fun! I am a big fan of property based testing for this reason alone!