BuildYourOwnLisp VS os-tutorial

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?

How to create an OS from scratch

My dude. Your functions have exactly the same names as his. Copying it from a different tutorial based on James Molloy's tutorial does not make it any less James Molloy's code.

I started out with this tutorial: https://github.com/cfenollosa/os-tutorial. It doesn't get you too far but it explains the basics very well, so check it out. After that I looked up James Molloy's kernel tutorials (look it up on Google, it's all on a website). Be advised that he's got a bunch of errors and bugs in the tutorial, there is a whole page on it on the osdev wiki titled known bugs in the JamesM kernel all something like that, but it's still great and gets you pretty far. After that, I chose to develop a FAT32 driver on my own, I can link some sources or my own code for you as well, but it's really up to you to follow what you like. I also found a great youtube series (https://youtube.com/@poncho2364?feature=share9), check out his osdev series, he also has some cool stuff there. And as I said, good luck on your journey and you can ask me in a DM as well if you get stuck somewhere!

tutorial : here

Yeah, I'm following cfenollosa's OS tutorial for guidance. You mentioned that you've seen the same code, with the same bug? What was the solution there?

hey, just in case you actually want to write an operating system, you should check out cfenollosa/os-tutorial: How to create an OS from scratch, it is an amazing tutorial that will get you from basic printing all the way to a command line interface!

You might be able to sink your teeth into something like this if you're interested in real os development, haven't got far myself but it's fun and you'll learn a lot https://github.com/cfenollosa/os-tutorial

So I made a 16-bit x86 toy OS in pure assembly. 3 months ago, I found a very fun tutorial on github that is about Operating system development. I read the first few chapter and from there I made a very simple, extensible (?) toy operating system that could run on hardware (yes, it is madness).