News for hackers. Stuff that matters.
Re:Is Typed Clojure worth the trouble? by sebastianconcpt on Tuesday June 23, 2015 @08:58PM (#9768903)
Thanks for the downvotes, I was referring to things beyond FP. The type system is a set of early restrictions (as opposing to late restrictions or runtime or late bound). But now you mention it, I'm curious about if you think the type checker allowed you and your team to reach the goals of the project faster or not.
Re:Is Typed Clojure worth the trouble? by dllthomas on Saturday June 27, 2015 @03:00PM (#9791179)
I had a system in C, with a goal of extremely low latency. This involved a small collection of threads, each serving a different role. Project goals would periodically change, and I would find myself needing to move some functionality from one thread to another. With some creativity, I was able to enlist the help of the type checker in assuring that a particular function ran only on a particular thread. This sped me up tremendously, as my tooling would point me to inconsistencies rather than having to reason them out myself.
Re:Is Typed Clojure worth the trouble? by boothead on Wednesday June 24, 2015 @10:10AM (#9771677)
Sometimes restrictions are useful...

Aside from that in Haskell the type system isn't usually a restriction. Experts in Haskell tend to use the type system to guide them towards a correct solution.

I'm not sure it possible to say that we couldn't have built something quicker in another language or stack. What I will say was that the underlying abstraction that we built our system on (streams of events) is very well suited to a Haskell implementation, and I can say with some certainty that building a solution that is as "correct" as the one we built would have been extremely challenging. The code also held together for longer than has been my experience in some other languages and communities.