Earlier quoted context omitted.
For me lisp in general was like that. But I just kept on until it clicked (mainly because I was getting sick of hearing all the hype and wanted to fully understand what all the fuss was about). A lot of people talk about when lisp clicks its an ahh-haa moment much like when your first programming language clicks and that is the best way to describe it. When it finally clicks it clicks but you have to put aside so muc…
Would you recommend I start playing around with Lisp before I do clojure?
Clojure for the Brave and True (2015)
71–80 of 106 posts
Re: Clojure for the Brave and True (2015)
#72Really 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)
#73Earlier quoted context omitted.
I think there is too much cognitive load in the first stages of learning Clojure for people who haven't had experience with functional programming, Lisps, Java, and Emacs on top of that if you are following Clojure for the Brave and True. So to barely get started you are tackling a new programming paradigm (functional), a new syntax (Lisp), getting error messages in Java, using tools that are complicated to setup and…
I still teach in and prototype in Light Table, even though it is losing its "instarepl". Live evaluation visually matched up to an expression removes a lot of the cognitive load. Clojure stack traces are a big mental overhead.
Re: Clojure for the Brave and True (2015)
#74Earlier quoted context omitted.
For me lisp in general was like that. But I just kept on until it clicked (mainly because I was getting sick of hearing all the hype and wanted to fully understand what all the fuss was about). A lot of people talk about when lisp clicks its an ahh-haa moment much like when your first programming language clicks and that is the best way to describe it. When it finally clicks it clicks but you have to put aside so muc…
> For me lisp in general was like that. But I just kept on until it clicked Not sure this is the right way... I mean, everything will "click" if you do the same, e.g. VB6, but do you want this?
Re: Clojure for the Brave and True (2015)
#75Earlier quoted context omitted.
Mind if I ask what isn't clicking? I've had the exact opposite experience, and have found it very easy to incorporate different libraries. Do you have experience with other lisps? There's certainly a learning curve with clojure and its frameworks.
Everything assumes you're a Java expert.
When one needs to look under the hood to solve performance or FFI issues, it is a requirement to know the "systems" language of the host platform, regardless how much we might love/hate it.
Re: Clojure for the Brave and True (2015)
#76I didn't enjoy this book; the examples used clojure constructs before introducing what they did making them arcane and difficult to understand, and it focused on the language without showing why you would use it or how to use it for real world projects. It's like... a detailed guide to the language, for people who already know clojure. I recommend 'Living Clojure' by Carin Meier for new comers. (Also, avoid the cloju…
Sometimes developers are like children, they need to be force feeded their vegetables.
You see this specially in the games industry, where language adoption is driven by OS vendor SDKs.
Re: Clojure for the Brave and True (2015)
#77Earlier quoted context omitted.
I think there is too much cognitive load in the first stages of learning Clojure for people who haven't had experience with functional programming, Lisps, Java, and Emacs on top of that if you are following Clojure for the Brave and True. So to barely get started you are tackling a new programming paradigm (functional), a new syntax (Lisp), getting error messages in Java, using tools that are complicated to setup and…
I still teach in and prototype in Light Table, even though it is losing its "instarepl". Live evaluation visually matched up to an expression removes a lot of the cognitive load. Clojure stack traces are a big mental overhead.
Re: Clojure for the Brave and True (2015)
#78Re: Clojure for the Brave and True (2015)
#79I love this book. Can someone recommend something similar for Go or Elixir?
Re: Clojure for the Brave and True (2015)
#80The 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."