4 ms·
(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
by jph 7y ago
(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. "Some defect type like memory
error, concurrency errors also depend on language primitives."
- vidro3 7y agoHow so? Typescript, along with most other languages is listed as 'No Statistically Significant Association" see fig 2. ETA: They actually did not assess Typescript in their reanalysis as most of the files were not actually Typescript, section 4.1.2
- faitswulff 7y agoThat's not at all what I got from the abstract: > ...only four languages are found to have a statistically significant association with defects, and even for those the effect size is exceedingly small. Emphasis mine.
- scott_s 7y agoI believe you are confusing the conclusions from the original paper with the claims from this paper. I think this is the case because this paper removes TypeScript from their dataset entirely: "4.1.2 Removal of TypeScript. In the original dataset, the first commit for TypeScript was recorded on 2003-03-21, several years before the language was created. Upon inspection, we found that the file extension .ts is used for XML files containing human language translations. Out of 41 projects labeled as TypeScript, only 16 contained TypeScript. This reduced the number of commits from 10,063 to an even smaller 3,782. Unfortunately, the three largest remaining projects (typescript-node-definitions, DefinitelyTyped, and the deprecated tsd) contained only declarations and no code. They accounted for 34.6% of the remaining TypeScript commits. Given the small size of the remaining corpus, we removed it from consideration as it is not clear that we have sufficient data to draw useful conclusions."
- xvilka 7y agoScala will really start to shine only after Scala Native[1][2] is ready. [1] http://www.scala-native.org http://www.scala-native.org [2] https://github.com/scala-native/scala-native https://github.com/scala-native/scala-native
- mannykannot 7y agoWhat features of Scala Native do you think will improve Scala code quality?
- mamon 7y agoLooks great, but will that happen in our lifetime?