> So, after looking into new and up and coming "better C's" like Odin and Jai, > I then found Nim.
I will never say anything negative about Jai (except that it's not actually available). A friend of mine watches all the Jai videos. I'm glad to see someone else recognizes brilliance. But Nim fits an important niche: Migration paths from C++ and Python. Because of the easy interop, you don't have to re-write an entire program all at once. It's amazing how many devs don't understand why that matters. If I were coding a giant program from scratch, there are lots of languages that I would consider, including Nim. But I'm not a Nim zealot. I use it because it's productive (Python-like syntax), fast (to compile and to run), conceptually simple, and gives me a way to migrate co-workers' code to a modern language gradually.
