1. Rust is very slow to compile. This is bad when rapid iteration is important.
2. Rust is a complex language. It wants to replace C++, not C, and gladly adopts features™ and the complexity that comes with that.
This is a good point. I wonder if the trend of saying C/C++ is to blame; that is, people see C, think C/C++, and then are incapable of realizing that C is, in fact, its own language, and not merely "C++ Jr." or C++ with some features removed.
There's a hole in the modern language world, from what I can see: We lack a simple, mid-level language which incorporates modern knowledge about language design, where by mid-level I mean that all resources (other than stack, perhaps) are managed by hand but it's reasonably simple to write cross-platform code.
In most cases, C would only be more practical on obscure or outdated hardware, though.
96% of the Linux kernel is written in C (https://github.com/torvalds/linux).
Update: Got to my system so I could actually look at available files accurately:
C Implementation (.c): 28269
C Header (.h): 20250
Asm (.S): 1323
Edits: Update section and removing "100% in C" and "5 sources files of assembly"The counter reports 1.2%, but if you click on that to show Assembly files it only reported 5 code results (it's not actually showing all Assembly, so you then have to click on "Unix Assembly" on the side).
That's not to say you couldn't cobble together a solution with enough elbow grease and FFI, but the cure may be worse than the disease.
> Reliability
While C is indeed a winner for obscure platforms, many language gets you perfectly covered for a "cross-platform" game.
> Performance
You can get equally good performance in Rust and C++.
> Simplicity
As he says, simplicity does not mean easy nor intuitive. Then it is a matter of opinion why simplicity should be a good thing. Personally, I prefer a complex but easier to use language than a simple but difficult to use language.
github.com/glouw/openempires
and my time spent with C has really just been manually implementing min heaps, circular buffers, ad hoc vectors, and a tier 1 dummy garbage collector.
All this stuff is readily available in C++, and I could have saved hundreds of hours by just using C++.
But, to one benefit, since I did all this work myself, I understand the machine better, and my compilation times are orders of magnitude faster than what I would have had if I chose C++. Additionly, since so few calls are even being made to the C standard library, the majority of the code exists in text, and easily inlines across all translations units with link time optimization. With C++, as except for templated library code, the majority of link time optimizations go to waste as calls to the standard library are binary linked.
Please ask yourself this before writing any code (For a cross-platform game).
By just reading this, I thought to myself if I were to write a cross-platform game in 2020, Is C necessary to accomplish this? Perhaps anything C can do, surely Rust can do it safer and arguably better.