I have no delusions of having enough time to ever follow through all of these videos, but it's still an idea that appeals to me. Something I'm curious about though:
If I wanted to follow along on a Mac instead of Windows, how different of a process am I looking at?
You can start with handmade penguin, which uses SDL2 instead of the windows API, this should be relatively easy to get working on a mac
https://davidgow.net/handmadepenguin/
From what I remember, he switched to 4coder because it supports modal editing that's better for his rsi problems. I guess he didn't care for vim or emacs with vi emulation. Casey also likes to support his "Handmade" network promoting simple C/C++ applications.
Most people don’t spend nearly enough time in a editor-specific language to keep it fresh and loaded at all time. So having to switch from a language/environment you’re fluent in to one you can merely get by in is a frustrating experience.
Watching Casey add some fairly powerful features in the editor in an hour or two, including using Windows APIs directly, was quite illuminating.
There are a few ports to other systems, but there's a small part of the process that will be opaque because someone other than Casey has done the legwork. By which I mean that you won't get any insight into how windows are built on OSX, how input is handled etc. because it's not part of the stream. As I understand it most of the code is platform agnostic, but the development process is windows biased and won't get to be cross platform until the engine is finished. I would love for someone to go over the unique pieces for mac in a supplemental video series the same way Casey does.
If I wanted to follow along on a Mac instead of Windows, how different of a process am I looking at?