4 ms·

I think the problem there was complacency, as the author mention in their mail. On the other hand, I totally do recommend that everyone picks up some tutorial o

by zaarn 9y ago

I think the problem there was complacency, as the author mention in their mail. On the other hand, I totally do recommend that everyone picks up some tutorial or guide or book on LISP and learns what the fuzz is all about. Even today, I feel like a lot of people could learn a lot from LISP and S-Expressions, both of which are powerful constructs. (Note: I'm not saying you should use LISP productively, it's something you should learn for the heck of it, not to actually use it)

phoe-krk 9y ago
> (Note: I'm not saying you should use LISP productively, it's something you should learn for the heck of it, not to actually use it) Well, I do, and I have to say that it can be done. It isn't a road often travelled and it results in people making remarks about your language choices, but as long as my software works, its development is fun for me and my co-coders do not complain, I don't think anything is wrong with my setup. :)
- zaarn 9y ago
  You can do that too. I think I may have expressed poorly; whether or not you want to use LISP in production, learn it anyway, because it's LISP.
baldfat 9y ago
People really should learn Racket through this book: "How to Design Programs, Second Edition" http://www.ccs.neu.edu/home/matthias/HtDP2e/ http://www.ccs.neu.edu/home/matthias/HtDP2e/ Dense and very complete into learning a Lisp. The one HUGE benefit is I see Racket moving into the most modern programming Lisp. Racket really looks like it has a future. 1) Concurrency and Parallelism (Without pull all your hair out) - http://docs.racket-lang.org/reference/concurrency.html http://docs.racket-lang.org/reference/concurrency.html 2) Great Documentation http://docs.racket-lang.org/reference/index.html http://docs.racket-lang.org/reference/index.html 3) It will make you a better programmer in other languages Racket's biggest problem - It's fun to use so everyone has their own solutions for many common problems.
- sedachv 9y ago
  +1 for HtDP. I think it is also a really valuable book for anyone coming from JavaScript who wants to actually learn how to do functional and reactive programming properly.

by zaarn 9y ago

phoe-krk 9y ago

> (Note: I'm not saying you should use LISP productively, it's something you should learn for the heck of it, not to actually use it) Well, I do, and I have to say that it can be done. It isn't a road often travelled and it results in people making remarks about your language choices, but as long as my software works, its development is fun for me and my co-coders do not complain, I don't think anything is wrong with my setup. :)

zaarn 9y ago
You can do that too. I think I may have expressed poorly; whether or not you want to use LISP in production, learn it anyway, because it's LISP.

baldfat 9y ago

People really should learn Racket through this book: "How to Design Programs, Second Edition" http://www.ccs.neu.edu/home/matthias/HtDP2e/ http://www.ccs.neu.edu/home/matthias/HtDP2e/ Dense and very complete into learning a Lisp. The one HUGE benefit is I see Racket moving into the most modern programming Lisp. Racket really looks like it has a future. 1) Concurrency and Parallelism (Without pull all your hair out) - http://docs.racket-lang.org/reference/concurrency.html http://docs.racket-lang.org/reference/concurrency.html 2) Great Documentation http://docs.racket-lang.org/reference/index.html http://docs.racket-lang.org/reference/index.html 3) It will make you a better programmer in other languages Racket's biggest problem - It's fun to use so everyone has their own solutions for many common problems.

sedachv 9y ago
+1 for HtDP. I think it is also a really valuable book for anyone coming from JavaScript who wants to actually learn how to do functional and reactive programming properly.