os-tutorial VS mal

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

>Would be interesting to see how the interpreter works actually...

It's quite easy to see, there are interpeters for Lisp in like 20 lines or so.

Here's a good one:

https://norvig.com/lispy.html

(It has the full code in a link towards the bottom)

There's also this:

https://github.com/kanaka/mal

Here is one implementation of a lisp (mal specifically) in matlab: https://github.com/kanaka/mal/blob/dcf8f4d7b9cf7b858850a04a0...

Only 260 lines of code, pretty concise :)

have a look at the crafting interpreters book, plus make a lisp (lisp is a great first language to make a compiler/interpreter for, just google "lisp compiler/interpreter" and you'll find lots of resources)

If you're really okay with the limitations of a tree-walk interpreter, you might want to check out MAL, which will teach you how to write a tree-walk interpreter for a LISP. The code for MAL has been translated to most popular languages, so you can work through the creation of an interpreter in the language of your choice. JLox would give you a bit more detail and a more complex language, but I'm not convinced that it's all that important.

Write a small programming language (lisp (https://github.com/kanaka/mal) or brainfuck) in C++ to learn the syntax more. This will teach you a lot about programming languages in general.

So I started some hobbyist game dev using Unity and realised that the full process of making a game has dependencies on a mass of lower-level skills including lighting virtual environments. As a hobbyist photographer I could see some useful analogies from lighting studios and other scenes

So I pivoted, and eventually made money, not from selling a game, but from developing tutorials about digital lighting. I was also able to contribute to a project at work that was making a product based on commercial games engine, not by actually coding it, but by helping to better estimate the costs of the asset generation required.

Coding Unity object scripts in C# also got me back into programming, and I went on to successfully build a self-hosting lisp interpreter following the Make a Lisp guidelines [0].

[0] https://github.com/kanaka/mal/blob/master/process/guide.md

Hijacking the top comment to add https://buildyourownlisp.com and https://github.com/kanaka/mal