Yeah. I think I’ll end up having to do platform-specific ifdefs with either pthreads or threads.h, so I guess I may as well use the much better established pthreads and get macOS support by default. In fact, I just now learned that even glibc didn’t support C11 threads until 2018, according to this https://sourceware.org/bugzilla/show_bug.cgi?id=14092#c10

Rust is a great language but it really has a lot of up-front costs. Whether you are learning it for the first time, or starting a new project, both. Python is always going to be faster “from idea to deployment.”

I think like the other person said, start with the Rust book. It really is a perfectly good introduction. But what I think you’ll find is if you want to be productive with Rust you will need to get the ground rules down or else you will be constantly tripping on the borrow checker and ownership rules. If you think you are getting somewhere with the book, try rewriting something you’ve done in Python. If that works out, great! If not, it’s OK to accept that Rust might not be worth your time.

Super Mario Bros got me in. It was my older sister’s game, so it was just something we had around the house for as long as I can remember. I think that’s a great first game to get into, because it has wonderful art and music, and simple, straightforward challenges to overcome.

On the flip side, Metal Gear Solid V: The Phantom Pain got me out of gaming for the most part. I had never been more excited for something than by the story being painted by the trailers leading up to the game’s release. I was already a big time MGS fan, and I’d say I still am. I even enjoyed MGS5 basically right up until the moment I beat it, and then I reflected on everything I just saw and felt utterly deceived. Empty open world, lots if time wasting interstitial moments, grind-based mechanics, and an unfinished story that didn’t need to take as long as it did to tell (and was stupid, too).