"Clinical Trials" For Programming Languages? 232
theodp writes "High school junior Charles Dawson's New Year resolution is to write a new program in different language each week. It's an ambitious project for someone of any age, and while it won't give him an in-depth appreciation of programming language differences, it'll certainly give him greater insight into the strengths of certain languages than would perusing the Hello World Wikipedia article. Lots of claims are made about the comparative productivity of programming languages, but have there been any landmark studies that measure the efficacy of a programming language's productivity claims in a 'clinical trial' of sorts? Would head-to-head tests against other languages be a better way of sorting out Popularity vs Productivity vs Performance claims, or is relying on more nebulous claims of superiority the best we can do?"
Programming Language Warning (Score:1, Funny)
If your using a programming language, but your language is not enough, then you should consult your doctor.
Call your doctor if your application worsens, or if you have unusual changes in mood, behavior, or thoughts of suicide.
See a doctor if you have high fever, stiff muscles, confusion, or having trouble swallowing.
Some adverse affects are: diarrhea, seizures, and flatulence.
Re:Simple Answer... (Score:5, Funny)
PHP is unparalleled for people who want to make a webpage without having to understand HTTP.
Or PHP for that matter...
(...kidding...)
actual clinical trials are nearly impossible (Score:4, Funny)
Some key features of "gold standard" clinical trials: 1) large enough sample size to draw statistically significant conclusions; 2) real illnesses, not a simulated laboratory setting; 3) a double-blind control group; and 4) long enough duration to measure real-world outcomes.
The programming-languages version would be to have teams randomly assigned to perform major (6+ month) programming projects in different languages, and then see their outcomes. For example, 40 game studios will continue to write their games in C++ as the control group, while you'll have the other 40 write them in Haskell. You probably want to iterate a few times as well to make sure that there's no first-game-in-a-new-language effect and to ensure that everyone is actually knowledgeable in the language being tested.
Oh, and it should be blind, so neither the teams nor the researchers know which language they're using.
Re:That is a beautiful start of a ... (Score:4, Funny)
long flamewar
To do this flamewar properly little Charlie Dawson should post his findings every week so we can keep this thing going until he finally realizes his dream of pissing off every programmer.
Re:Simple Answer... (Score:5, Funny)
Master Po: The Tao gave birth to machine language. Machine language gave birth to the assembler. The assembler gave birth to the compiler. Now there are ten thousand languages. Each language has its purpose, however humble. Each language expresses the Yin and Yang of software. Each language has its place within the Tao. But do not program in COBOL, Grasshopper, if you can avoid it.
Grace Hopper: My name isn't Grasshopper, and I will program in whatever I want!
Re:That is a beautiful start of a ... (Score:5, Funny)
It's only a flamewar until you agree that there are 2 types of programming languages:
- Those everyone bitches about
- And those nobody uses
Re:That is a beautiful start of a ... (Score:5, Funny)
pissing off every programmer.
Well, everybody except LISP programmers ofcourse, as that will turn out to be the best language.