os-tutorial VS Crafting Interpreters

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).

Build an Interpreter (Chapter 14 on is written in C)

I’m guessing you’ll have to work with the scopes in the resolver:

https://github.com/munificent/craftinginterpreters/blob/mast...

Better open an issue/request wiki edit at https://github.com/munificent/craftinginterpreters/wiki/Lox-implementations

I'm late to the party, but I want to say thank you for sharing this. It's inspiring to look at how much you've built and (hopefully) enjoyed the process of building! I'm loving everything -- your site, your language design, your docs, your builtin libraries, your dev tools. Beyond impressive. People like you are the ones who make HN one of my best places on the internet.

For context on where I'm coming from, about two weeks ago I picked up Crafting Interpreters [1] for fun. I'm finding your clear-yet-concise Compiler internals [2] to be particularly compelling reading, and jumping back and forth between those "how this all works" docs and the live example of this language you actually built do a WASM-compiled tree-blowing-in-the-wind animation is just... just wow. So freaking cool!

I also enjoyed reading the comment thread that inspired you to start on Yaksha and seeing how this project has a wholesome start as inspiration-by-programming-hero. I hope you recognize that a few years later you've now ascended from inspiree to inspirer. I also hope you're still having tons of fun building out Yaksha!

[1] https://www.craftinginterpreters.com/

[2] https://yakshalang.github.io/documentation.html#compiler-int...

There are books which will talk you through the process. Crafting Interpreters is highly spoken of; I used Writing an Interpreter in Go, because I like Go. Then there's Compilers: Principles, Techniques, and Tools (the "Dragon Book"). This is considered heavy, but a classic, it's been around since '86.

I cannot recommend Crafting Interpreters by Robert Nystrom enough, it covers a lot of the stuff you need to know, completely for free.

Crafting Interpreters is a fun primer on language design. It has a complete roadmap to build a fairly simple language, twice. There are some topics it won't touch on, like static type systems, but it provides a great introduction so that you can start tinkering and learn by doing.