4 ms·

http://www.infoq.com/presentations/Simple-Made-Easy http://www.infoq.com/presentations/Simple-Made-Easy (this is so fundamental to this topic that it is require

http://www.infoq.com/presentations/Simple-Made-Easy http://www.infoq.com/presentations/Simple-Made-Easy (this is so fundamental to this topic that it is required watching to even have an opinion on this subject) http://clojure.org/rationale http://clojure.org/rationale http://www.dustingetz.com/2011/05/05/how-to-become-an-expert-swegr.html http://www.dustingetz.com/2011/05/05/how-to-become-an-expert... http://www.dustingetz.com/2012/10/07/java-sucks-because-idiomatic-java-is-bad-code.html http://www.dustingetz.com/2012/10/07/java-sucks-because-idio...

MatthewPhillips 14y ago
You don't have to convince me of OOP's faults; Clojure is my favorite language. But I write code for a living, mostly in OOP because that's where the jobs are, and I do not write very many bugs caused by OOP's poor design. I write bugs when the business is ill-defined, or when I misunderstand how a library's APIs are supposed to work, or when I'm careless and don't consider "what do I do if this function returns false"; all stuff that will come up in FP as likely as it will in OOP.