5 ms·

> This is because of how much of the unix clone ecosystem has been built around C workflows Absolutely correct. > convincing linus and sysadmin greybeards to

> This is because of how much of the unix clone ecosystem has been built around C workflows Absolutely correct. > convincing linus and sysadmin greybeards to modernize linux That's not what I'm suggesting. Anything that's already written in C can and probably should continue to be so. What I'm suggesting is that people who prefer to work in other languages should have an easy way to make their work available beyond their own language community. I'm not talking about interpreted/scripting languages here. I'm talking about compiled/systems languages. Stuff that gets linked together, or that should be able to use some sort of dlopen/FFI back and forth fluidly despite multiple languages being involved. There's some work to be done there, but everyone seems to prefer hiding in their own language bunker instead of reaching out to others.

pjmlp 8y ago
There are solutions, but only at platform level. JVM, CLR, COM, UWP, DEX, TIMI, ILE are all possible approaches with various degrees of success and most of them also have C implementations available. It is almost impossible to get some kind universal ABI between OSes and languages without an extra level of indirection.
slededit 8y ago
The problem is that other languages necessarily place more restrictions on how their data can be used in order to gain all their nice features. Since you can't control the caller you lose all those guarantees. Because of that it will never be easy to interop across higher level languages. C works well here because its low level enough that it expects few guarantees. Just keep the stack aligned and balanced and it will mostly be happy.