News for hackers. Stuff that matters.
Re:Object-Oriented Programming: A Disaster Story by alkonaut on Wednesday January 20, 2016 @04:43AM (#10936941)
> It shouldn't be very difficult to prove that a particular programming paradigm is better along some axis than another

I think it would be one of the hardest things to ever prove scientifically actually. Basically the only valid method I'd accept is having a large group of people who are non-developers, then train half of them in one paradigm and the other in another. Then have both groups solve the same set of problems.

The problem with this experiment is that in order to get useful results is that you need a good group of people that are representative of programmers (i.e. people that don't know programming, but can and are willing/able to learn). Say you can find 1000 mechanical engineering students for example. Great. Next they need to be trained. How long does that take? A year or two? Finally they need to solve the problems, which should be large problems. Next the solutions to the problems should be carefully evaluated. I'd say the experiment if done in academia would be ridiculoulsy expensive and time-consuiming.

Numerous studies such as on static vs dynamic typing have used tiny programming experiments done by a small groups of students doing trivial exercises over the course of a day. I'd say they give little or no insight in how experienced developers handle large problems.

It's very hard to do it as a natural experiment too. A large company could try giving the same task to a team of OO developers, as it does to a team of FP developers. This has happened and the result is usually that the FP developers do it in half the time with half the bugs and twice the enthusiasm. However -- can we know that the people who ended up being FP developers weren't just better developers than the OO devs? I'd wager that "enthusiasts" are more commonly drawn to FP today, so the base of FP developers is a group that is on average "better" than the OO devs. So while I don't doubt that FP is "better" in most scenarios, I also belive the FP group would have done a better job with the OO language as well.

Re:Object-Oriented Programming: A Disaster Story by pron on Wednesday January 20, 2016 @04:51AM (#10936965)
> Basically the only valid method I'd accept is having a large group of people who are non-developers, then train half of them in one paradigm and the other in another. Then have both groups solve the same set of problems.

I'd settle for two competitors working in the same domain producing similar products using different paradigms, reporting significantly different costs throughout the project's lifetime (including maintenance). Or even a single company reporting a vast decline in costs after switching paradigms, provided that the project is big enough and lasts long enough (five years at a minimum, a decade is preferable). Of course, the more domains and more cases per domain the better. This isn't theoretical. We had numerous case studies of this sort in the late '90s-early '00s showing a very big cost reduction when moving from C/C++ to Java, in projects ranging from enterprise software to defense.

Re:Object-Oriented Programming: A Disaster Story by alkonaut on Wednesday January 20, 2016 @05:11AM (#10937061)
The problem with two competitors is that you still can't be sure that the firm that used FP either had "better" developers who would have done the project better at the other firm too. I have met almost no bad developers who do and enjoy FP, and I have met tons of bad OO developers. Actually, even OO developers that just know of the concept of FP are way in my experience way better OO devs than those who don't.

A company switching paradigms is a better test, since the same developers are involved, and presumably they would be less experienced in the new paradigm than the old. If they still produce better software that is a good indication that it was a good switch. Still, there may be a number of companies that did this and failed because they couldn't reach profitability with a new code base, or couldn't fill vacancies and so on. Like I said, it's very hard.

Re:Object-Oriented Programming: A Disaster Story by pron on Wednesday January 20, 2016 @05:26AM (#10937133)
> The problem with two competitors is that you still can't be sure that the firm that used FP either had "better" developers who would have done the project better at the other firm too.

Yes, but over enough such cases, you can average this out. Also, better developers are more expensive, so that is factored into the cost.

Re:Object-Oriented Programming: A Disaster Story by andybak on Wednesday January 20, 2016 @05:10AM (#10937057)
> I'd settle for two competitors working in the same domain producing similar products using different paradigms <snip>

I think you'll easily find the example you seek. In fact I think you'll probably find several.

Unfortunately they are all likely to support different conclusions.

Re:Object-Oriented Programming: A Disaster Story by pron on Wednesday January 20, 2016 @05:27AM (#10937135)
> Unfortunately they are all likely to support different conclusions.

... which means that the case is not so clear cut, which may suggest that the increased effectiveness of some methods is not universal but restricted to specific domains or even specific team compositions.

Re:Object-Oriented Programming: A Disaster Story by lomnakkus on Wednesday January 20, 2016 @04:56AM (#10936993)
> I think it would be one of the hardest things to ever prove scientifically actually. Basically the only valid method I'd accept is having a large group of people who are non-developers, then train half of them in one paradigm and the other in another. Then have both groups solve the same set of problems.

... and have them maintain the resulting software for years and years. Otherwise you're mostly "just" looking at learning curve, I should think.

Re:Object-Oriented Programming: A Disaster Story by alkonaut on Wednesday January 20, 2016 @05:17AM (#10937089)
Yes, or the problem to solve could be starting with an existing (bad) code base, so maintenance and development are both done in the experiment.
Re:Object-Oriented Programming: A Disaster Story by lomnakkus on Friday January 29, 2016 @04:02PM (#10998472)
In all fairness I think that would actually be a tougher situation, all things considered :).

It's a sort of weird testament to the efficiency (not efficacy) or inscrutability of computing that it's hugely in demand even if there's little evidence that it actually matters for anything important.

Re:Object-Oriented Programming: A Disaster Story by cowardlydragon on Thursday January 21, 2016 @12:00PM (#10946525)
Yes, it shouldn't be hard to decide if some program will halt or infinitely loop, right?

Right?