I find the repeated "yolo" qualifications very tiresome, yawn-inducing.
At least in this article:
the term "classic C" is still used.
I don't expect for a moment that Fil-C might supplant normal C under normal circumstances. Calling normal C "yolo-C" is dishearteningly pompous. Just because you've invented a C environment with a different tradeoff, people not interested in it are not automatically irresponsible (which is what you are suggesting with "yolo", of course).
Back in the Usenet days we used to call C development, cowboy programming, while they called safer languages like Ada, Modula-2 and Object Pascal, straightjacket programming.
I am perfectly fine with Yolo-C nickname.
Yolo - You only live once. Perfectly describes what happens when you have a segfault in C. It dies.