4 ms·
Are there actual facts to back up claims to productivity boosts or failures with a given paradigm across large numbers of programmers and organizations? I'm no
by goatlover 9y ago
Are there actual facts to back up claims to productivity boosts or failures with a given paradigm across large numbers of programmers and organizations?
I'm not a big fan of Java or C++, but they have been used to write tons of code running software that's complex and in wide use.
Maybe a functional, non-mutable approach is better, but until it has a similar widespread use and enough time for people to complain about it and suggest new superior paradigms, I'm not sold on the truth of these claims.
It sounds more like preference and opinion than fact. Also, I can't help but wonder if it's the C++/Java model of OOP that's more than issue than OOP itself. Would the same complaints be made of Smalltalk? Personally, I prefer the OOP of Ruby than that of Java, and don't really see a problem with using it.
- userbinator 9y agoI'm not a big fan of Java or C++, but they have been used to write tons of code running software that's complex and in wide use. If other languages were used, perhaps they would not need to be so complex and resource-consuming, but this is also why any "actual facts" which you're looking for are difficult to find: you'd need to essentially do the same project multiple times in different languages and perform a very highly controlled comparison, and there are numerous other confounding factors. Failures or successes alike can easily be spun into blaming the languages. IMHO there is no one perfect paradigm for everything, and the only failure is in promoting one as panacea or trying to view all of programming in the same way. I think trying to classify languages or code as strictly OOP, procedural, functional, etc. and shunning "hybrids" or even basic common-sense pragmatism for dogmatic purity has had the greatest negative effect on productivity.
- maxxxxx 9y ago"I think trying to classify languages or code as strictly OOP, procedural, functional, etc. and shunning "hybrids" or even basic common-sense pragmatism for dogmatic purity has had the greatest negative effect on productivity." That's it. Rigid ideology is the real problem. In software engineering and other areas too, eg politics.
- pmarreck 9y agohttp://macbeth.cs.ucdavis.edu/lang_study.pdf http://macbeth.cs.ucdavis.edu/lang_study.pdf
- tanilama 9y ago> Are there actual facts to back up claims to productivity boosts or failures with a given paradigm across large numbers of programmers and organizations? NO. Functional people claim that, but never had a proof, since there aren't that many people using it to build large systems. Thus this myth lives on. :)
- willtim 9y agoWell in this instance Functional programming languages allow one to easily embrace the relational paradigm and avoid all the complexity from an ORM. Note that it has never been "proved" that OOP is more productive than anything else either.
- tanilama 9y agoWhich is exactly the point. There is no proof of superiority, it is just a choice flavor
- willtim 9y agoActually most of us do not have a choice, OOP languages, tools and frameworks are usually forced upon us. At least OOP languages are finally adopting functional features, but if one really wants to favour immutability and composition (modern OOP advice), one needs a functional-first language.
- di4na 9y agoErlang in the meantime, functionnal and actor model, does have proofs.