Well, you did also say "If it ain't broke don't fix it", so we might be agreeing. You wouldn't want any new programming language to roll its own SSL library rather than using OpenSSL or GnuTLS, would you?
I wouldn't want a project to write its own SSL library no, but I would not start a new project in C, and if I had an existing C codebase I would seriously think about migrating it to a safer language (unless it needed particular C features. Crypto code does, because it needs to resist timing attacks, but that's a very rare case).
In my opinion, this is like moving away from C due to its security record.