Lmst

> One of the conclusions that we reached was that the "object" need not be a primitive notion in a programming language; one can build objects and their behaviour from little more than assignable value cells and good old lambda expressions. — #GuySteele on the design of #Scheme in #DougHoyte's #LetOverLambda has me thinking #LambdaTheBase as a helpful metaphor, something to demystify all the compact forms that can be overwhelming for the occasional would-be progammer.
https://letoverlambda.com/index.cl/guest/chap2.html

Screenshot of the first 3 paragraphs of the chapter linked to in the post. The description of closures has me thinking, again, of Laozi(Lao Tzu, Lao Tse):
"Closures are one of those few curious concepts that are paradoxically difficult because they are so simple. Once a programmer becomes used to a complex solution to a problem, simple solutions to the same problem feel incomplete and uncomfortable. But, as we will soon see, closures can be a simpler, more direct solution to the problem of how to organise data and code than objects. Even more important than their simplicity, closures represent a better abstraction to use when constructing macros—the topic of this book."

I think we need a #MinimalistProgram for everything. I've been wondering what the equivalent of #CKOgden's #BasicEnglish might be for #Racket or #Scheme. The #FossAndCrafts Scheme tutorial mentioned #LambdaTheUltimate and reminded me of #DougHoyte's #LetOverLambda book where he quote #GuySteele on primitives. I have Laozi in mind and want to think of #LambdaTheBase or #BasicLambda... With just lambda and an approach like #TheSchemersGuide learning could be in a very minimalist situation.

いいなあマクロとはコンパイル（トランスパイル）である
うーん、痺れる～ #letoverlambda

#LetOverLambda

Client Info