Note that the "C committee" was actually the X3J11 committee of ANSI, the American National Standards Institute. In other words, it was just one committee within an organization with a long history of developing cross-industry standards. As such, their job in theory wasn't to invent new technology, but rather to adjudicate between technologies proposed and demonstrated by competing industry vendors.
Like many other modern languages, Rust is a mono-implementation, where the same organization is both developer and standards committee, while at the same time trying to fund itself (without revenue from either standards docs or the compiler) and balance external commercial and non-commercial interests.
There are advantages and disadvantages to each approach, but they are very, very different. (and in a world of cutting edge open-source compiler technology, I'm not sure the approach which resulted in ANSI C is even viable today)
Like many other modern languages, Rust is a mono-implementation, where the same organization is both developer and standards committee, while at the same time trying to fund itself (without revenue from either standards docs or the compiler) and balance external commercial and non-commercial interests.
There are advantages and disadvantages to each approach, but they are very, very different. (and in a world of cutting edge open-source compiler technology, I'm not sure the approach which resulted in ANSI C is even viable today)