10 ms·
On Lisp
- nonrecursive 13y agoInstructions for printing it with lulu: http://www.lurklurk.org/onlisp/onlisp.html http://www.lurklurk.org/onlisp/onlisp.html . I did this about a month ago and the copy I received was great.
- pmelendez 13y agoThe link to the lulu's book is not working for me... Can you please share it?
- mark_l_watson 13y agoI also printed it on Lulu several years ago - worked great.
- vamega 13y agoJust tried to do this, and found that the cover image size doesn't seem accurate anymore. What did you do for the cover?
- arh68 13y agoReally? I just made the book and ordered it last night and the cover (the 13MB png) looked like it lined up exactly. The first cover-uploader had a 10MB limit but the other worked fine (not the design-your-own, the 1-piece-cover-designer).
- deleted 13y ago[deleted]
- vamega 13y agoTurns out I was trying to get a hardcover. It worked just fine with a paperback.
- damianknz 13y agoCheers to PG for making this available.
- yonaguska 13y agoI've been meaning to read this for quite some time, but I've been told that the idioms and coding style is outdated, or not very good. This isn't going to stop me, but I'd like to know from some experienced lispers what problems I might encounter. Especially as I'm pretty inexperienced myself. I definitely won't know what to look for.
- nonrecursive 13y agoThe book uses common lisp, so you'll need to know how to read that. Otherwise I think you should be fine. It's not a book about idioms or coding styles, but about thinking in lisp. If the code examples are confusing, it'll be because you're not sure what something means in common lisp or because you're learning new ideas, not because the code is poorly written. So, if you treat it as a book of ideas as opposed to "teach yourself x language in 24 hours", you should be OK :)
- officemonkey 13y agoHowever, if you ARE looking for a "teach yourself Lisp in 24 hours" type of book, you could do a lot worse than "Practical Common Lisp" by Peter Seibel (http://www.amazon.com/Practical-Common-Lisp-Peter-Seibel/dp/1590592395 http://www.amazon.com/Practical-Common-Lisp-Peter-Seibel/dp/...).
- socillion 13y agoPCL is also available for free at http://www.gigamonkeys.com/book/ http://www.gigamonkeys.com/book/
- 6d0debc071 13y agoAnother rec: Land of Lisp - http://landoflisp.com/ http://landoflisp.com/ - is also very good if you're looking to get up to speed with the absolute bare bones, so to speak, fairly quickly.
- outworlder 13y ago
- ceautery 13y agoI look forward to reading this, however I object to the first reviewer comment: "The first book that really explains what Lisp is all about." No, I think the first book to explain that was Godel, Escher, Bach.
- systems 13y agoOT how is arc progressing?
- drcode 13y agoThe Clojure inventor (Rich Hickey) took most of the good ideas from arc and all the arc enthusiasts have pretty much changed horses long ago to Clojure. I think arc still has some good points related to code brevity that noone else has fully duplicated yet.
- unz 13y agoLisp is a dangerous language that shouldn't be taught or used these days. There are plenty of superior programming techniques. Mathematical programming - linear programming, finite domain constraint programming, constraint logic programming, logic programming, relational programming Static functional programming - ml, haskell A good modern introduction to programming is Concepts, Techniques, and Models of Computer Programming, by Peter Van Roy and Saif Haridi. It's far superior to the commonly mentioned lisp book Structure and Interpretation of Computer Programs.
- pmelendez 13y ago>"Mathematical programming - linear programming, finite domain constraint programming" Huh? I am not sure if you are trolling or if you copied and pasted that without further investigation, but comparing operation research algorithms (such as linear and finite domain constraint programming) with a programming language is at the very least... disingenuous. > "Lisp is a dangerous language" That's a very strong and weird statement, would you mind to explain? because to me is completely the opposite.
- unz 13y ago(putting aside the rudenss and cluelessness of your comment ...) Operations research type algorithms can be thought of as forward chaining compared to prolog's backward chaining. Prolog implementations usually integrate them in because they are more efficient in many cases. Lisp's dangerousness was why ML was invented by Robin Milner.
- andyidsinga 13y agoI think I should read it in emacs ...running on an ec2 instance
- betterunix 13y agoGreat book, but not if you are just starting out with Lisp. For that, see PG's other book: http://www.amazon.com/ANSI-Common-LISP-Paul-Graham/dp/0133708756/ref=sr_1_1?ie=UTF8&qid=1377483440&sr=8-1&keywords=ansi+common+lisp http://www.amazon.com/ANSI-Common-LISP-Paul-Graham/dp/013370... Also make sure you check the errata for On Lisp, there are a few examples that you will really need the errata for.
- pavelludiq 13y agoActually a much better place to start is Practical Common Lisp: http://gigamonkeys.com/book/ http://gigamonkeys.com/book/ Or if you are now to programming in general: http://www.cs.cmu.edu/~dst/LispBook/ http://www.cs.cmu.edu/~dst/LispBook/
- thurn 13y agoWhat percentage of the techniques in this book are also applicable to Clojure programming? I don't know a lot about how the two macro systems differ.
- nickik 13y agoA lot of it. Clojure has a Common Lisp like macro system. There are some slight changes where clojure tried to make things a little simple, and the syntax is a lot diffrent. I think there are people on the internet who have implmented most of the example in clojure.
- AeroNotix 13y agoNo reader macros, though.
- arohner 13y agoOn Lisp is great for learning about macros, and what is possible. That being said, what is idiomatic in CL is not necessarily idiomatic clojure. For example, pg tends to like anaphoric macros, (http://en.wikipedia.org/wiki/Anaphoric_macro http://en.wikipedia.org/wiki/Anaphoric_macro), while Clojure tends to eschew them.
- oskarth 13y agoHave a look at http://thinkrelevance.com/blog/tags/on-lisp http://thinkrelevance.com/blog/tags/on-lisp to see Stuart Halloway going through On Lisp in Clojure.
- chongli 13y agoA fair amount of the examples involve mutation; a practice that Clojure discourages. A lot of the macros are very instructive, however.
- brudgers 13y agoIndeed, On Lisp has an excellent discussion of mutation and its use in programs written in a functional style. In discussing destructive functions, Graham describes the ways in which they can be used with reasonable safety - e.g. immediately mutating a list newly created by a mapping function. The reasons one might do so in Clojure are likely to bear similarity to those provided by Graham - speed and memory - despite the vastly greater resources of today's computers versus those of 1991.
- mark_l_watson 13y agoWowza, it has been 20 years since this book was published. Time goes by too quickly :-(
- neurostimulant 13y agoAny advice or link for someone new to Lisp like me? Also, is there any good open source project using Lisp that I can fork/download and tinker with? I'm still having problem wrapping my head around Lisp. Even implementing some simple algorithms in Lisp took some time for me. I think this is due to the fact that I learned to program in C. Nowadays I work mainly with python/ruby/javascript, but I got the feeling that I could improve myself as a programmer by learning Lisp.
- eru 13y agoYou could have a look at the software below Hacker News. It's written in the Arc Lisp dialect (which itself is implemented on top of the Racket Lisp dialect). Apart from Racket, Clojure is also a nice Lisp to get started with. It runs on the JVM. I'd advice against learning Common Lisp as your first Lisp these days, even though Common Lisp is what On Lisp is about.
- pavelludiq 13y agoI'd advise exactly the opposite. While clojure and racket are excellent languages, they are very different from one another and CL. Telling someone to learn python or ruby if they ask about learning lua isn't a good advice, is it?
- eru 13y agoOh, if your goal is to learn one of the Lisps, then don't spend any time on Common Lisp. It's old and ugly. Similar, if someone asked about a modern scripting language, I'd send them away from Perl in favour of Python or Ruby. If they goal was explicitly Perl (or Common Lisp) that would be a different thing, though.
- serf 13y ago>>Oh, if your goal is to learn one of the Lisps, then don't spend any time on Common Lisp. It's old and ugly. why? I don't find that at all, and a large reason for learning common lisp is as a learning exercise to become more intimately familiar with lambda calculus and s-expressions. The increased expressivity of clojure (for example) may hinder the very thought processes that make lisp a dialect worth learning. Of course they are both fine languages, but most people now advocate the learning of a LISP not for practicalities sake, but rather just to demonstrate real life things that those sets of languages do differently than nearly every other language, and to allow the programmer to take from those experiences and apply them to their language of choice. From THAT standpoint, i'd advocate CL first, if not only for forcing the user of the language to experience the follies of certain practices, such as the namespace issues that Clojure tried to fix about CL.
- javajosh 13y agoHas anyone every tried to visualize lisp with a treemap? Maybe that would take care of the massive indentation problem that makes lisp so hard to read (for me).
- jdale27 13y agoIt's 2013, and the top comment on a story about Lisp (on HN, a site written in Lisp) is complaining about syntax? Seriously, how much time did you actually spend learning/using Lisp before giving up because it had a "massive indentation problem"?
- IvarTJ 13y agoSurely expressing personal issues with Lisp's syntax is valid, especially if a possible solution is offered. If you see at least some of the larger codebases written in Lisp, it is natural to be overwhelmed by the level of indentation, which will cause the code to wrap under many editor setups.
- jdale27 13y agoI've heard people complain about parentheses, but indentation isn't usually the issue. I challenge you: I looked at your personal website, and you seem to claim experience in Java and C. Show me a large codebase in Lisp and a large codebase in Java or C where the Lisp codebase is dramatically less readable than the Java or C codebase due to indentation.
- javajosh 13y agoYou seem very upset. Calm down. I just had an idea that it might be fun to represent lisp code in a treemap. Or rather a zoomable treemap like this: http://bost.ocks.org/mike/treemap/
- heretoo 13y agoPerhaps like these? http://foldr.org/~michaelw/emacs/ http://foldr.org/~michaelw/emacs/
- akavel 13y agoDid someone try (and possibly succeed) converting it to epub, by chance?
- gernotk 13y agoAlso take a look on "Let Over Lambda" by Doug Hoyte about advanced macro techniques: http://letoverlambda.com/ http://letoverlambda.com/ It's a pretty enjoyable book if you don't mind its preachiness. :-)
- niuzeta 13y agoI thought 'oh, is this a new book'? Then I looked at the date. It seems as though all 'classical' sources on lisp or functional paradigm are either two decades old, or just-out-yesteryear. What happened in between?