This was a good book. It would have been better if he had a more critical perspective of the language. As much as I love Rich Hickey and Clojure, the language does have pitfalls and rough edges, and this book was a little too starry-eyed to tackle them head-on like Crockford's book on JavaScript.
I agree. A sibling comment recommends "Joy of Clojure" but I feel that's better as a second or third book. My personal recommendation, YMMV as always, is Kyle Kingsbury's "Clojure from the Ground Up" series https://aphyr.com/tags/Clojure-from-the-ground-up , then "Clojure Applied", then "Joy of Clojure". Hard to say an ideal order for the last two -- "Clojure Applied" is more approachable IMO, but "Joy of Clojure" is…
Clojure for the Brave and True (2015)
81–90 of 106 posts
Re: Clojure for the Brave and True (2015)
#82Really appreciate the access to the book online http://www.braveclojure.com/clojure-for-the-brave-and-true/ more likely to buy products that you can see. This years challenge, learn two new languages. Clojure might be one of them. The reason? Lisp based and in spite of the fact it uses cough , Java (JVM), it runs on JavaScript. A better language to run/work with JavaScript. That is a good enough reason to learn and u…
I hear this a lot, but it totally mystifies me. You lose all the good parts of clojure when you go into the js runtime; stm, parallel processing, java interop, hot reloading, and it pulls in some really quite large js dependencies, and it's impossible to debug. Even console logging becomes a case of 'convert to readable object and log' using special helpers. What's the benefit? I don't see any meaningful reason to us…
Re: Clojure for the Brave and True (2015)
#83Re: Clojure for the Brave and True (2015)
#84The entire second chapter is devoted to learning emacs. I find this to be a baffling editing decision. "Thanks for reading this book, but before we cover what you came for, let's do this other completely orthogonal thing first."
Re: Clojure for the Brave and True (2015)
#85I love Clojure, and have spent most of the last seven years in a Clojure REPL inside Emacs. But it still doesn't feel like critical mass has been reached. If anything, large efforts like Incanter have mostly died off, because most Clojure people are smart and resourceful enough to build their own stuff. There's an aversion to frameworks and a reliance on gluing together smaller libraries, which is totally valid as a…
Kind of reminds me of this: http://web.archive.org/web/20160304105922/http://www.lambdas... "Another feature about this guy is his low threshold of boredom. He'll pick up on a task and work frantically at it, accomplishing wonders in a short time and then get bored and drop it before its properly finished. He'll do nothing but strum his guitar and lie around in bed for several days after. That's also part of the patt…
Re: Clojure for the Brave and True (2015)
#86I love Clojure, and have spent most of the last seven years in a Clojure REPL inside Emacs. But it still doesn't feel like critical mass has been reached. If anything, large efforts like Incanter have mostly died off, because most Clojure people are smart and resourceful enough to build their own stuff. There's an aversion to frameworks and a reliance on gluing together smaller libraries, which is totally valid as a…
Kind of reminds me of this: http://web.archive.org/web/20160304105922/http://www.lambdas... "Another feature about this guy is his low threshold of boredom. He'll pick up on a task and work frantically at it, accomplishing wonders in a short time and then get bored and drop it before its properly finished. He'll do nothing but strum his guitar and lie around in bed for several days after. That's also part of the patt…
Re: Clojure for the Brave and True (2015)
#87Earlier quoted context omitted.
I agree. A sibling comment recommends "Joy of Clojure" but I feel that's better as a second or third book. My personal recommendation, YMMV as always, is Kyle Kingsbury's "Clojure from the Ground Up" series https://aphyr.com/tags/Clojure-from-the-ground-up , then "Clojure Applied", then "Joy of Clojure". Hard to say an ideal order for the last two -- "Clojure Applied" is more approachable IMO, but "Joy of Clojure" is…
is there any rhyme or reason to the order of the links on that page? the welcome post is bottom left.
Re: Clojure for the Brave and True (2015)
#88Earlier quoted context omitted.
I'm not sure when your last exposure to the ClojureScript ecosystem was, but almost nothing you mention is a problem as of 2016: debugging, hot reloading, large JS deps, etc. I'm biased, but I think ClojureScript is the best way to use the JavaScript platform today. Awesome core library, consistent build process, best of breed tooling, persistent data structures, flexible syntax (JSX is madness compared to hiccups);…
Got a link with specifics? I've never seen breakpoints & source maps working properly; just a series of blog posts by various people who've tried and failed to get it working.
Re: Clojure for the Brave and True (2015)
#89Earlier quoted context omitted.
Got a link with specifics? I've never seen breakpoints & source maps working properly; just a series of blog posts by various people who've tried and failed to get it working.
That's like 2 years ago. Source maps work fairly well today.
how do you do it then?
Re: Clojure for the Brave and True (2015)
#90This is by far the best book around for learning Clojure from scratch (IMO). If you always wanted to learn Clojure but never had the time, 2017 is the right year, and Clojure for the Brave and True is your companion. Buy it, or just read it for free on the website. (Disclaimer: I'm not in any way associated to the book or the author, I'm just super thankful for all the times this book has helped me to learn new thing…