3 ms·
He actually touched on this towards the end of the presentation. To simplify, he states that Clojure is about data and Scala is about types. When accommodating
by jaxytee 13y ago
He actually touched on this towards the end of the presentation. To simplify, he states that Clojure is about data and Scala is about types. When accommodating dynamic data, it's easier to use Clojure because of the ubiquity of Maps as the primary data type and the nice handling if Null values via Clojure's Nil type. In Scala, dynamic data is dealt with using the Option Monad, and this adds layers of complication to your code.
- stormcrowsx 13y agoYeah but by and whole the talk was more about cons of Scala than pros. If your going to describe a language in terms of another you should list what both are good and bad for. It was a very biased talk that makes it sound like Clojure fixes just about everything, in reality Clojure works well in a band of problems that Scala is not well suited for. This talk is actually better than most but in general when people compare two languages they bash one and praise the other excessively. I'd like to see an end to that trend and for speakers to start saying what a tool is meant for and what its not meant for.
- jaxytee 13y agoVery true that this talk did seem to be bias to Clojure. As and Scala user myself, I think his critique of Scala was fair.