According to Wikipedia : " Clojure is a modern dialect of the Lisp programming language. It is a general-purpose language supporting interactive development that encourages a functional programming style, and simplifies multithreaded programming. Clojure runs on the Java Virtual Machine and the Common Language Runtime. Clojure honors the code-as-data philosophy and has a sophisticated Lisp macro system."
Stuart Halloway in his Programming Clojure book …
…the best innovations in programming may have in fact occurred in the late 60s and early 70s, when Lisp was invented and then disregarded in favor of C++, and the best hypnotist who ever lived is very probably the late, great Milton Erickson, whose techniques have been carefully documented, thoroughly explained, and widely not emulated. It's easy to become a great programmer if you work at it, but nobody does. The same is true of hypnosis; excellent schools exist, excellent books exist, …
From zero to Lisp autofellatio in sixty seconds.
Reddit and HN commenters scratched their heads over the post, reading it out of context. I hope they find this. I'll post it, but it's not my priority. In fact, I'm annoyed at Peter Cooper for tweeting about it; otherwise I would have made it through the day without visiting either Reddit or Hacker News, and days like that do me better in terms of productivity than this other kind of day.
I'm going to suggest that …
…exposed to functional programming, was during an AI subject where we had to do some Lisp along with having to learn a whole slew of other concepts. Needless to say, functional programming wasn't the emphasis in that subject; many people struggled and struggled badly. We certainly had some exposure to closures during that subject, but who had time to think about that, it was all most people could do to try and wrap their heads around a new style of programming when they had just spent two …
…technology called a browser, and it's not too much of a stretch to call Emacs a Lisp browser.
Tools — we've come a long way in fifty years. We started writing machine code directly, then we grew assemblers, linkers, and compilers. Today, few developers will go through their career without using a debugger, profiler, lint tool, or applying an automated refactoring. There are a lot of development tasks that can be offloaded directly to the computer, leaving the programmer free …
I just finished The Little Schemer . I liked it. It's a very short book. Most of my time was spent doing the exercises, which were very worthwhile. There were a few sections I had to read twice, but the book was far more accessible than say SICP . If you've never coded in Lisp or Scheme or if you're looking for some good exercises for your coding fu, I highly recommend this book. Happy hacking!
…isn't burdened with having to recursively pass a reference to itself.
If you didn't understand any of the above, don't sweat it. I read it twice, and I still barely get it ;) However, I think I now understand why Paul Graham used that name for his startup incubator, Y Combinator . Paul Graham is a Lisp guy, and his Y Combinator is a startup meant to recursively launch other startups ;)
…features together, you have a metaprogramming environment that I would argue is as powerful as what Lisp macros give you, although I'm sure there are some hardcore Lisp programmers out there that would disagree with me.
Satish>> How was experience of taking part in the Ruby Programming Challenge For Newbies ( RPCFN)?
Paul>> I've really enjoyed it. It's a great exercise to come up with a solution to a problem and then be able to compare your solution to what …
Now Lisp suddenly used S-expressions for both code and data. The interesting
thing is how code was represented in Lisp. It's in fact very simple: The first
element in the list is the operator/function and the rest is the
operands/arguments: (+ 1 2) (plus-five 5) (factorial 10)
This makes Lisp a very simple language to implement. You need very few
primitives before you have a fully working Lisp system. In fact, I would
recommend watching James Coglan's screencast. …
…their languages didn't have macros [ Joey's note: Macros are a Lisp feature that smug Lisp weenies often use in the never-ending "Why my language is better than your language" argument]
Four Ugly Failure Modes and How to Avoid Them
Confusing correlation with causation
I think it's one of the most prevalent diseases in the business world
Ruby is not a silver bullet
Was the success of many Ruby projects [such as Rails and Twitter] because …