61–70 of 138 posts
Earlier quoted context omitted.
JS also has more ways to shoot yourself in the foot than any other language I've worked with.
PHP? C?
Seems like they're just doing associations, and not controlling for a lot of factors. For example, you can come up with some narratives to explain a lot of these findings: * Python, JS, PHP, Java, C++ are all very common first languages; I'd imagine the average experience level for these is dragged down a bit compared to others like Golang, Haskell, or Scala. One of the recent Stack Overflow Developer surveys found G…
That would be interesting. I also have a feeling it would be incredibly difficult to accurately control for social differences in language communities.
Earlier quoted context omitted.
JS also has more ways to shoot yourself in the foot than any other language I've worked with.
PHP? C?
(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…
Scala will really start to shine only after Scala Native[1][2] is ready. [1] http://www.scala-native.org [2] https://github.com/scala-native/scala-native
Seems like they're just doing associations, and not controlling for a lot of factors. For example, you can come up with some narratives to explain a lot of these findings: * Python, JS, PHP, Java, C++ are all very common first languages; I'd imagine the average experience level for these is dragged down a bit compared to others like Golang, Haskell, or Scala. One of the recent Stack Overflow Developer surveys found G…
Earlier quoted context omitted.
JS also has more ways to shoot yourself in the foot than any other language I've worked with.
PHP? C?
Despite these three languages giving far too much freedom to the programmers (which some might even like), high-quality code can be written in all three of them, as long as intelligent and strict coding guidelines are thoroughly followed.
Earlier quoted context omitted.
The practice that most reduces the incidence of tests is code review: https://kevin.burke.dev/kevin/the-best-ways-to-find-bugs-in-...
Emphasis on "Formal code review" which is practiced in far fewer shops than "code review". For those who don't happen to know the difference, formal code review basically uses a check list of common best practices and possible defects to look for versus doing each code review ad-hoc.
Earlier quoted context omitted.
PHP? C?
I agree that JS is not substantially "worse" than some other languages. Despite these three languages giving far too much freedom to the programmers (which some might even like), high-quality code can be written in all three of them, as long as intelligent and strict coding guidelines are thoroughly followed.
And of course lots of out of band(non-language) processes and tools that influence this like unit testing/code reviews/strict coding guidelines. But it's always nicer when it's prevented at the language level as opposed to out of band.
(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…
Scala will really start to shine only after Scala Native[1][2] is ready. [1] http://www.scala-native.org [2] https://github.com/scala-native/scala-native
I’ve read a lot of code as a consultant. The best codebase I’ve read had almost no comments and was written in erlang. Besides that every codebase I’ve read in Golang were super clear and of excellent quality for the exception of one that was written by java developers. I can say I hated reading C because of maccros and different build systems. I hated C++ codebases because people abused generics. And I hated Java th…
> because of the verbosity and the directory structure and all the layers of abstractions and all the factories and all the singletons and all the Fair, but a lot of those abstractions make life more difficult for new programmers (Why do I have to look through 12 classes to find out what this button does?), but make life much easier when you know the code base and have to maintain and extend it. Or, legit question -…
Yes. Except on the actively powerless languages (mostly C and Go), people write code on other languages with the same flexibility that all that indirection creates on Java, but they use much simpler structures.