Comments on: What killed Lisp could kill Haskell as well. http://enfranchisedmind.com/blog/posts/what-killed-lisp-could-kill-haskell-as-well/ programming, politics, & other religious issues Fri, 12 Mar 2010 09:19:33 +0000 hourly 1 By: Destillat #11 | duetsch.info - Open Source, Wet-, Web-, Software http://enfranchisedmind.com/blog/posts/what-killed-lisp-could-kill-haskell-as-well/#comment-37383 Destillat #11 | duetsch.info - Open Source, Wet-, Web-, Software Mon, 08 Mar 2010 12:16:59 +0000 http://enfranchisedmind.com/blog/?p=1277#comment-37383 [...] Clojure wont win the battle but may win the war [...] [...] Clojure wont win the battle but may win the war [...]

]]> By: Brian Hurt http://enfranchisedmind.com/blog/posts/what-killed-lisp-could-kill-haskell-as-well/#comment-37345 Brian Hurt Sun, 07 Mar 2010 03:34:02 +0000 http://enfranchisedmind.com/blog/?p=1277#comment-37345 The type hints are A) slightly clunky, and B) excessively limited. The type hints are A) slightly clunky, and B) excessively limited.

]]> By: Michael http://enfranchisedmind.com/blog/posts/what-killed-lisp-could-kill-haskell-as-well/#comment-37340 Michael Fri, 05 Mar 2010 16:23:03 +0000 http://enfranchisedmind.com/blog/?p=1277#comment-37340 If I remember correctly, Clojure supports type hints, right? Wouldn't that support a more 'static' style? If I remember correctly, Clojure supports type hints, right? Wouldn’t that support a more ’static’ style?

]]> By: Slobodan Blazeski http://enfranchisedmind.com/blog/posts/what-killed-lisp-could-kill-haskell-as-well/#comment-37336 Slobodan Blazeski Fri, 05 Mar 2010 12:42:04 +0000 http://enfranchisedmind.com/blog/?p=1277#comment-37336 Clojure is going nowhere until there is an it just works implementation of it. Currently there is plenty of plugins to choose from for any java ide but none of them just work. The amount of early adopters who are ready to cope with configuring and hunting through dependencies is insignificant. Until clojure is ready to cross the chasm the war is far from won. http://www.ericsink.com/Act_Your_Age.html Clojure is going nowhere until there is an it just works implementation of it. Currently there is plenty of plugins to choose from for any java ide but none of them just work. The amount of early adopters who are ready to cope with configuring and hunting through dependencies is insignificant. Until clojure is ready to cross the chasm the war is far from won.
http://www.ericsink.com/Act_Your_Age.html

]]> By: Laurent Petit http://enfranchisedmind.com/blog/posts/what-killed-lisp-could-kill-haskell-as-well/#comment-37335 Laurent Petit Fri, 05 Mar 2010 08:39:45 +0000 http://enfranchisedmind.com/blog/?p=1277#comment-37335 Hello Brian, Please note that, while indeed not having compilation-time type correctness analysis, clojure has introduced, since version 1.1.0, the notion of pre and post conditions, that you can place on any method. And they can be removed at runtime, depending on the value of a global flag. So with this feature, it's totally possible for you to write type checks in pre-conditions, thus allowing you to minimize a debug time by having the code "fail fast and close to the error". See http://clojure.org/special_forms#Special%20Forms--%28fn%20name%3F%20[params*%20]%20exprs*%29 for detail on the pre- post- conditions feature. Hello Brian,

Please note that, while indeed not having compilation-time type correctness analysis, clojure has introduced, since version 1.1.0, the notion of pre and post conditions, that you can place on any method. And they can be removed at runtime, depending on the value of a global flag.

So with this feature, it’s totally possible for you to write type checks in pre-conditions, thus allowing you to minimize a debug time by having the code “fail fast and close to the error”.

See http://clojure.org/special_forms#Special%20Forms–%28fn%20name%3F%20params*%20]%20exprs*%29 for detail on the pre- post- conditions feature.

]]>