Worth a read because it is one the most condescending computing books I have ever read. While reading I got the impression that I read the text of a really immature fanboy in a web forum of the 2000s. I hope the author has matured by now. Seriously, don't buy this book.
Or, you know, the author knows his stuff and is deservedly condescending in an industry of trends and cargo cults. As in arts and politics, some curmudgeons are needed in every field, if not for anything else, to show that there's another way than the mainstream. (They don't have to be perfectly right either -- it's having a strong perspective that counts, nobody is 100% right anyway).
Let over Lambda – Common Lisp Book (2008)
21–30 of 99 posts
Re: Let over Lambda – Common Lisp Book (2008)
#22Earlier quoted context omitted.
Common Lisp was finalized in the 90s. And it's not its fault that the other languages haven't caught up yet.
Still, its a trip to hell to maintain any lisp codebase -- especially if it contains macros. I think it is actively hostile to collaborative programming, and that is a structural problem where there is no remedy but obscure programming patterns (which are amplifying these problems in some instances). With that in mind -- boasting about 'the most advanced language' is a bit of a stretch -- to say the least...
Re: Let over Lambda – Common Lisp Book (2008)
#23Earlier quoted context omitted.
Common Lisp was finalized in the 90s. And it's not its fault that the other languages haven't caught up yet.
Still, its a trip to hell to maintain any lisp codebase -- especially if it contains macros. I think it is actively hostile to collaborative programming, and that is a structural problem where there is no remedy but obscure programming patterns (which are amplifying these problems in some instances). With that in mind -- boasting about 'the most advanced language' is a bit of a stretch -- to say the least...
Re: Let over Lambda – Common Lisp Book (2008)
#24Worth a read because it is one the most condescending computing books I have ever read. While reading I got the impression that I read the text of a really immature fanboy in a web forum of the 2000s. I hope the author has matured by now. Seriously, don't buy this book.
https://letoverlambda.com/index.cl/guest/chap6.html Yeah, the sixth chapter sure bashes on Scheme a lot. :/
Re: Let over Lambda – Common Lisp Book (2008)
#25Earlier quoted context omitted.
I thought it was great, but I know it's not a book for snowflakes. When I hear someone say "this is right" or "this is wrong", I am able to effortlessly interpret this as "I believe this is right/wrong". It's just being efficient with language. I don't need people to add extra words for fear of offending me. Maybe the author was immature. That's great. Let it remind you what it's like to be young and so excited about…
Do you think it is useful for a Lisp noob?
Re: Let over Lambda – Common Lisp Book (2008)
#26Earlier quoted context omitted.
I thought it was great, but I know it's not a book for snowflakes. When I hear someone say "this is right" or "this is wrong", I am able to effortlessly interpret this as "I believe this is right/wrong". It's just being efficient with language. I don't need people to add extra words for fear of offending me. Maybe the author was immature. That's great. Let it remind you what it's like to be young and so excited about…
I'm a long time Lisper myself but also couldn't get through this book. Maybe it's because am a snowflake, but my eyes rolled so often I was scared they'll get stuck in the up position.
Re: Let over Lambda – Common Lisp Book (2008)
#27Earlier quoted context omitted.
Common Lisp was finalized in the 90s. And it's not its fault that the other languages haven't caught up yet.
Still, its a trip to hell to maintain any lisp codebase -- especially if it contains macros. I think it is actively hostile to collaborative programming, and that is a structural problem where there is no remedy but obscure programming patterns (which are amplifying these problems in some instances). With that in mind -- boasting about 'the most advanced language' is a bit of a stretch -- to say the least...
Which would easily make decades old and still maintained Lisp implementations unmaintainable, since they contain zillions of macros themselves.
Re: Let over Lambda – Common Lisp Book (2008)
#28Earlier quoted context omitted.
Common Lisp was finalized in the 90s. And it's not its fault that the other languages haven't caught up yet.
Still, its a trip to hell to maintain any lisp codebase -- especially if it contains macros. I think it is actively hostile to collaborative programming, and that is a structural problem where there is no remedy but obscure programming patterns (which are amplifying these problems in some instances). With that in mind -- boasting about 'the most advanced language' is a bit of a stretch -- to say the least...
Re: Let over Lambda – Common Lisp Book (2008)
#29Earlier quoted context omitted.
Still, its a trip to hell to maintain any lisp codebase -- especially if it contains macros. I think it is actively hostile to collaborative programming, and that is a structural problem where there is no remedy but obscure programming patterns (which are amplifying these problems in some instances). With that in mind -- boasting about 'the most advanced language' is a bit of a stretch -- to say the least...
Do you say that out of experience? That is certainly not my _experience_. Lisp codebases tend to be easily "appropiable"
Re: Let over Lambda – Common Lisp Book (2008)
#30Worth a read because it is one the most condescending computing books I have ever read. While reading I got the impression that I read the text of a really immature fanboy in a web forum of the 2000s. I hope the author has matured by now. Seriously, don't buy this book.
Or, you know, the author knows his stuff and is deservedly condescending in an industry of trends and cargo cults. As in arts and politics, some curmudgeons are needed in every field, if not for anything else, to show that there's another way than the mainstream. (They don't have to be perfectly right either -- it's having a strong perspective that counts, nobody is 100% right anyway).
The words you're looking for are "writes poorly."