8 ms·
Thanks!
by pg 13y ago
Thanks!
- bliti 13y agoHow has the book aged?
- coolsunglasses 13y agoAbout as well as anything related to Common Lisp. It's abstract enough that some of the macro patterns are reusable in Clojure, but we don't often use them in Clojure. Anybody that wants a deeper understanding of Lisp should read, but with the understanding that it's not a shake-n-bake recipe book. The last time I wrote an anaphoric macro (let alone the scope-capturing one), the Clojure IRC channel had a heart-attack.
- do-it-good 13y ago>> the Clojure IRC channel What's the full address?
- coolsunglasses 13y ago#clojure on irc.freenode.net
- bliti 13y agoI read it about ten years ago. Do not remember anything, because I was never able to find work as a Common Lisp programmer. Would have been fun. I know that things in the lisp community change very slowly, and wanted to know if the book was still relevant. Might give it a second go. Is Clojure "lighter" (for a lack of a better term) than lisp?
- coolsunglasses 13y agoClojure is more pliable, yet more robust. Easier to learn in some respects, yet deeper if you look for it. I've found it easier to teach Clojure than I had Common Lisp in the past, yet Clojure has helped me to grow more as a programmer. There's very little that you can do in CL, that you cannot in Clojure. That which you can't is often very limited and unimportant ultimately. There are many things that are either impossible or hopelessly painful in Common Lisp that are commonplace in Clojure. It is shocking how much code I write in Clojure is either: 1. Stateless 2. Stateful and multi-threaded, yet thread-safe.
- bliti 13y agoMay you tell what type of systems do you work with? i.e., Web, server, enterprise intranet, etc.
- coolsunglasses 13y agoWeb (frontend and backend), SOA, data warehousing, scale-out.
- pg 13y agoThough this may sound odd, I don't know. I haven't read any of it for a long time.
- brudgers 13y agoany time.