News for hackers. Stuff that matters.
Re:Haskell in Production: 12 Months Building ApiEngine by jasonjackson on Thursday May 23, 2013 @02:18PM (#5758460)
Cool, this can be done in any language with typing. For languages with dynamic typing, you would just check the type at runtime.
Re:Haskell in Production: 12 Months Building ApiEngine by beala on Thursday May 23, 2013 @03:01PM (#5758737)
There is a big difference between static and dynamic checking. In a statically checked language like Haskell the error is guaranteed to be caught at compile time rather than maybe being caught runtime.
Re:Haskell in Production: 12 Months Building ApiEngine by gizmo686 on Thursday May 23, 2013 @06:03PM (#5759813)
One of the main things that drew me to Haskell is how little effort it takes to define a new type.
Re:Haskell in Production: 12 Months Building ApiEngine by awj on Friday May 24, 2013 @05:19PM (#5765238)
It can be, yes, but it's easier to do so in Haskell. Some of the compiler extensions allow you to push truly crazy invariants through type checking.

Also, for most dynamic languages, checking the type at runtime goes against the grain of the language. Python or Ruby code that is littered with type checks is often unnecessarily brittle.