3 ms·
The 'easier to read' part is valid maybe for the first week of working with a Lisp (commenting as a part of a team which switched from mostly-Java to only-Cloju
by dm3 13y ago
The 'easier to read' part is valid maybe for the first week of working with a Lisp (commenting as a part of a team which switched from mostly-Java to only-Clojure several months ago).
Pros for Clojure:
* Faster code -> result cycle. No need for compilation (except for AOT-compiling releases).
* Absence of static typing helps in some of the domains, e.g. web applications. We have successfully used Prismatic's Schema[1] in places where a stable data interchange format was needed.
* Binary compatibility. No need to recompile libraries for different Clojure versions.
* Community oriented towards simplification. People mostly try to mimic Rich Hickey and Clojure.core development approach.
* Orientation towards small libraries. I haven't yet had a need to use a framework written in Clojure (although Pedestal[2] seems interesting).
[1] https://github.com/Prismatic/schema https://github.com/Prismatic/schema
[2] http://pedestal.io/ http://pedestal.io/
- lmm 13y agoHow complete is core.typed? Does it have a good story for scala type features I've come to depend on (covariance, some kind of typeclass-like functionality, higher kinds)?
- dm3 13y agoCore.typed appears to have some higher kind and variance support (as seen in the user guide - https://github.com/clojure/core.typed/wiki/User-Guide https://github.com/clojure/core.typed/wiki/User-Guide). Type classes can be mimicked via multimethods or protocols.