What makes lisp so unique is the way its code is structured - you definitely can’t miss all those parentheses. In this section of the series, I discuss the cause for such a representation and how that makes lisp unique in terms of how it views its code as data as code (aka homo-iconicity).
Further reading Python disassembler Homoiconity Byte Code S-expressions Common Operator Notation Abstract Syntax Tree The Blub Paradox Call to collaborate If you’re someone who shares the dream of making lisp popular and mainstream so that we can use it for our jobs and don’t have to switch to blubs to make a living (without denting its charm of course) , consider contributing to the notes and hit me up via mail or any of the other media I’m present on.
This is an auxilliary post collating resources for the recent video I posted …
The Pipeline All the ideas, resources that I want to process, any miscellaneous questions I have, are fed into the input-queue in the buffer All the manipulation takes place in these buffers - they’re org-files and I use org-roam to maintain the connections whenever a node set ripens and is worth sharing, I write a post or publish a video.
This is the first in a series of blog posts that follow the educational common lisp series on my youtube channel as an auxilliary.
I’ll be summarizing the videos in these blogs and be using these to point to references and additional resources that further elaborate the matter.
This post is about why you should consider learning common lisp and how I intend to execute the plan of building an end to end resource index while simultaneously being able to learn more about the language myself.
