دانلود کتاب مرجع ضروری کلوژر (Clojure)

The expressiveness of a language is often described as the speed at which ideas can be translated into working software. Part of the expressiveness comes from the language itself in terms of syntax, but another fundamental part comes from the standard library which is usually provided out of the box. A good standard library liberates the programmer from the most mundane tasks like connecting to data sources, parsing XML, dealing with numbers and a lot more. When the standard library does a good job, developers are free to concentrate on core business aspects of an application, boosting productivity and return of investment. Consider also that a deep knowledge of the standard library is often what distinguish an average developer from the expert. The expert can solve problems more elegantly and faster than the beginner because, apart from having solved the same problem before, they can compose a complex solution by pulling small pieces together from the standard library Finally, the standard library contains solutions to common programming problems that have been battle-tested over generations of previous applications. It is certainly the case for Clojure. The robustness and reliability that comes with that kind of stress is difficult to achieve otherwise. There will be possibly just a handful of cases where something in the standard library won’t fit your needs and will need to be reimplemented. Dvorak users often claim huge benefits compared to QWERTY users. Here’s one comparison, including other kind of layouts: lifehacker.com/should-i-use-an-alternative-keyboardlayout- like-dvorak-1447772004 manifesto.softwarecraftsmanship.org The short answer is: they don’t need to be. Also consider that a language specification doesn’t always mandate the content of the additional language utilities and tools. The standard library is then free to be described and documented in a less formal way. Clojure doesn’t have a formal language specification, let alone a standard library specification. Clojure’s informal (and pragmatic) approach is also its main weakness in terms of documentation: the language and the standard library are described in a very essential style which is often considered beginner-unfriendly . A lot of effort has been put lately into improving Clojure documentation although, at the time of this writing, the standard library is still lacking a comprehensive and centralized reference.