First they made "C the good parts" by gathering all the various C bits then in use to make something portable and called it C89.
Then they made "C the good parts" by removing all the parts that made C slow to write and called it Perl.
Then they made "C the good parts" by making C easier but still fast and called it Java.
In the meantime, we've gotten Objective-C and C++, which were attempts to make C better while preserving backwards compatibility. C++ has gone on to spawn its own legacy of "No actually, these are the good parts" with D, Clay, Rust, and various half-steps along the way that want some of the features of C++ but not all of the features of C++.
I don't think they'll stop, because as it turns out, people use tools for different reasons and it's very rare that a general purpose tool solves your very specific problem perfectly. I'm inherently skeptical of any "X the good parts" because the "good parts" are domain specific.