The reason C is seen as the universal language for FFI in some circles has more to do with Unix being popular than with C being particularly well suited for interoperability.
We know this, because in ecosystems that don't start with the Unix process as the definition of a program, C isn't what gets chosen. Within the JVM or CLR, for example, source languages don't usually interop via C ABIs. Those platforms have their own blessed languages, and they don't work like C does.
Dan Gohman /
npub1lv…xe8lq
2024-01-10 17:11:08
Author Public Key
npub1lv23llnug449h8k3ej9pz0edmeynjx7cl4p9h5r9q8uggm9qaw2s5xe8lqPublished at
2024-01-10 17:11:08Event JSON
{
"id": "e8eef619f074e6c5408d40cbb4fcffb78b46a32212f3604f02fca1874c5e7456",
"pubkey": "fb151ffe7c456a5b9ed1cc8a113f2dde49391bd8fd425bd06501f8846ca0eb95",
"created_at": 1704906668,
"kind": 1,
"tags": [
[
"proxy",
"https://hachyderm.io/users/sunfish/statuses/111732763433449485",
"activitypub"
]
],
"content": "The reason C is seen as the universal language for FFI in some circles has more to do with Unix being popular than with C being particularly well suited for interoperability.\n\nWe know this, because in ecosystems that don't start with the Unix process as the definition of a program, C isn't what gets chosen. Within the JVM or CLR, for example, source languages don't usually interop via C ABIs. Those platforms have their own blessed languages, and they don't work like C does.",
"sig": "0e6e57dfa2bf63cef04c8d5dbacdd5096d8ba32e720a630baa6a6a29a47c619e17e5cb82c0500fee582f384330e5973cd7e94a710e7d5e65ff97c137c74b026b"
}