> The first step should be to show that the github dataset can be used to say anything about quality and productivity of things like language choice. The datas

> The first step should be to show that the github dataset can be used to say anything about quality and productivity of things like language choice. The dataset can be used to say how defect rates compare across programming languages, that's important given that in CS and PL research these things are usually claimed left and right without any evidence. What the dataset can't say is how that translates to quality and productivity, as that would require a lot more than just commit messages. But at the same time it's something people already have some rough ideas about, like that people writing in low level rigid inexpressive languages are less productive than in high level flexible expressive languages.