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

“DAMN! I ran the red light. But actually it wasn’t my fault, the light switched to yellow just as I was checking my rear mirror, I had no time to react by the time I glanced forward again. Oh well. It’s fine.”

– Maybe me.

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.

I think the “upsell” (Lord help me for calling it this) is that it integrates with Office365, or in a corporate environment, AD. So by provisioning it once you have every component interconnected. If you’re used to Edge at home you will not be hesitant to want to use it at work. To say nothing about getting non-corporate home users into Bing and, ideally, Microsoft’s OpenAI-ified Bing.

It’s all very nasty work.