tag:blogger.com,1999:blog-6579772240267288367.post59059101327083285..comments2023-06-05T08:45:12.716-04:00Comments on kwblog: Simple Made EasyKevin Berridgehttp://www.blogger.com/profile/13759114853595462455noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6579772240267288367.post-56502134895267899092012-03-13T15:58:30.340-04:002012-03-13T15:58:30.340-04:00Dan S. pointed me to both your blog post and the H...Dan S. pointed me to both your blog post and the Hickey presentation. I haven't watched Hickey yet but you both touch on a subject we've been talking about quite a bit at Within3 lately. I spent many years as an OO snob and I'm starting to become an OO contrarian. Every tool can be used for both good and evil. I'm starting to think we've swung the OO pendulum too far to the evil side. I'm starting to feel as though many OO "best practices" create a bunch on unnecessary complexity. We may be screwing ourselves.<br /><br />It will probably come as no surprise to you that I've become pretty obsessed with Clojure lately. I'm working on a side project with some friends and I'm doing the work primarily in Clojure. I'm loving it. One of the best things about Clojure is the strong Java interop. When OO lends itself better to a particular task you can use an OO language (Java/Groovy/JRuby/Jython/take-your-pick) then use Clojure for everything else. It's a very powerful model.Jerry D'Antoniohttp://jerryknowscode.comnoreply@blogger.com