Learning to program in C++ takes a great deal of time and a lot of real-world practice. Learning to program *well* in C++ can take years or decades, and some people never do.
Unless you use C++ for your job, few people have the time or energy to devote to learning low-level languages like C/C++. This is why there are millions of times more people who are proficient in higher level languages like Python, Java, and C#.
Of course, in some ways it may "better" to write any software in something like C++, but you could say the same about assembler. That doesn't mean it's the only way or even the best way. Having millions of times more qualified programmers available to work on a project is a devastating advantage.
In this case I suppose it depends on what purpose the author of this API has in mind for his wonderful creation. At the moment there is really only a tiny group of people to be able use his work to create things for the community, especially considering the total and complete lack of documentation. If you thought about how many programmers were interested in ARk as well as being experienced enough in C++ and motivated enough to dig through the API source code to try and work it all out... well I'd say you're going count them on two hands.
Just by creating some documentation he could massively expand his audience and allow all his wonderful work to be utilised by a much larger group of programmers.
And by considering expanding the work to include wrappers for C# or Java or even Python, you could take your potential audience into the thousands of people.
Just my thoughts. No offence intended to anyone
