On the Impact of Programming Languages on Code Quality
1–10 of 138 posts
Re: On the Impact of Programming Languages on Code Quality
#2I skimmed the paper. I misunderstood the results.
Re: On the Impact of Programming Languages on Code Quality
#3It’d be interesting to see whether programmers’ preferences uphold the division posited by the study, or whether they are widely variable—eg is it likely that if you prefer ruby you’ll also prefer typescript over JavaScript, if you prefer Haskell you’d choose clojure over c++ etc.
Re: On the Impact of Programming Languages on Code Quality
#4I mean, this type of study is somewhat open to interpretation. It's not like everyone should arrive to the exact same numbers..
Re: On the Impact of Programming Languages on Code Quality
#5...deleted I skimmed the paper. I misunderstood the results.
"Unfortunately, our work has identified numerous problems in the FSE study that invalidated its key result."
Re: On the Impact of Programming Languages on Code Quality
#6The winners in this paper are Clojure, Haskell, Scala.
I look forward to seeing Rust added. The authors go into substantial detail about what they consider errors, and in my personal experience Rust solves many of them. See e.g. "Some defect type like memory error, concurrency errors also depend on language primitives."
Re: On the Impact of Programming Languages on Code Quality
#7(Edited-- I was reading the original paper, which showed good results for TypeScript; the new paper linked above refutes that result. My mistake. Thanks to the posters who corrected me!) The winners in this paper are Clojure, Haskell, Scala. I look forward to seeing Rust added. The authors go into substantial detail about what they consider errors, and in my personal experience Rust solves many of them. See e.g. "Som…
ETA: They actually did not assess Typescript in their reanalysis as most of the files were not actually Typescript, section 4.1.2
Re: On the Impact of Programming Languages on Code Quality
#8I remember Emery being quite confused at the methodology in the paper, and he was very confused with one aspect of it, which was how they came to conclude that C was more bug prone (something about void * being able to cast to everything? It was a while ago...)
Glad to see he wrote a rebuttal, a little awkward watching a professor debate with the paper's author :)
Re: On the Impact of Programming Languages on Code Quality
#9Maybe off topic, but isn't the language in the abstract a bit aggressive? I mean, this type of study is somewhat open to interpretation. It's not like everyone should arrive to the exact same numbers..
The idea is to take a clear position, which can be attacked if wrong.
Re: On the Impact of Programming Languages on Code Quality
#10In the early days of Python, some employers used it as a way to filter for candidates who were ahead of the curve. I believe Paul Graham mentioned Lisp being good for attracting better programmers, although I can't find the reference anymore [1]. If there's any value in this kind of filter, the effects will show up in the programmers' output.
1. I'm having a hard time finding references for these assertions; the best I've found is some Reddit posts and Joel Spolsky's post on finding great developers: https://www.joelonsoftware.com/2006/09/06/finding-great-deve...