BuildYourOwnLisp VS Angular

Build Your Own Lisp

Create your own meta-circular evaluator: https://www.buildyourownlisp.com/

I don't know about C++ but there is this incredible course on C by learning to build your own Lisp. https://www.buildyourownlisp.com/

I find the best way to learn technical topics is to build a simplified version of the thing. The trick is to understand the relationship between the high level components without getting lost in the details. This high level understanding then helps inform you when you drill down into specifics.

I think this book is a shining example of that philosophy: https://www.buildyourownlisp.com/. In the book, you implement an extremely bare-bones version of lisp, but it has been invaluable in my career. I found I was able to understand nuanced language features much more quickly because I have a clear model of how programming languages are decomposed into their components.

If you still want to produce a toy project in C I would suggest to build your own LISP ;-)

If you're after a lisp, MAL on Github (By kanaka) and https://www.buildyourownlisp.com/ are good.

Build your own Lisp is cool but offloads the language grammar and the parsing to the author's mpc library, this is already way overkill for what I'd like to do.

Writing a Lisp - https://www.buildyourownlisp.com/

Lisps are also a good language if you want to know how languages work. They are very easy to make an interpreter for. There are good tutorials for that at https://github.com/kanaka/mal and https://www.buildyourownlisp.com/.

Anyone have any input on:

https://www.buildyourownlisp.com/

It's been in my bookmarks for a long time but I've never really had time to really start it. The "who is this for" page say:

"This book is for anyone wanting to learn C, or who has once wondered how to build their own programming language.".

Well, I'm fairly competent in C (but not great) but would like to get a glimpse of what it's like to build my own language. Is it worth the time?

/** * https://github.com/angular/angular/blob/75a186e321cb417685b2f13e9961906fc0aed36c/packages/core/src/render3/reactivity/untracked.ts#L15 * * packages/core/src/render3/reactivity/untracked.ts * **/ export function untracked(nonReactiveReadsFn: () => T): T { const prevConsumer = setActiveConsumer(null); try { return nonReactiveReadsFn(); } finally { setActiveConsumer(prevConsumer); } }

source: https://github.com/angular/angular/issues/46542

Besides the dangers, mentioned by Angular docs (infinite loops, change detection errors), there is another thing, that might be quite nasty: effects are executed in a reactive context, and any code you call in effect, will be executed in a reactive context. If that code reads some signals, they will be added as dependencies to your effect. Here Alex Rickabaugh explains the details.

In June 2023, the Angular team raised a new RFC to implement control flow syntaxes within Angular. They gave the following rationale for introducing control flow syntax:

For scheduling, I use awesome code I found in the Angular source code.

Just to give you more context, I led the migration of several AngularJS applications to the newer Angular Framework. My client finally decided to make that move following the AngularJS deprecation announcement (stay up to date please 🙏)️.

Link — angular/CONTRIBUTING.md

Angular v17 was released some months ago with a ton of new features, a brand new logo and the new blog angular.dev.