>>9Forgot the common mistake is "FFI to C code will reduce the need to write libs/code/programs" is gesture of obsolescence.
The "C replacement" must replace all of C.
If (C ecosystem can survive without X) and (X ecosystem can't survive without C FFI), programmers will choose the safer option with the larger ecosystem. However when X ecosystem can compete with C ecosystem with its own libraries/OSes/programs, people will start switching due C many flaws(which X fixes in some way).
This means alot of code needs to be ported.
C FFI is a tempting because it seems to be easy way out: in reality its only a temporary crutch that cannot be relied on.
Every piece of C code that is relied on is contributing to C survival and ecosystemic dominance.