Hacker News Reader

Would be interesting to know which ffi backend library is used for each.

libffi, dyncall, self-written, a jit library, llvm, ...

In my tests these varied wildly. It has nothing to do with the language using these.

I believe most of these if not all of the languages have a native C compatibility layer. Java has JNI. Zig and Rust inherently use llvm. Go has cgo. nim compiles to C. luajit has its own FFI notation. Etc.

This would be worth mentioning on the project issue page, methinks. The author might not want to do the work but it's a very good thing to keep in mind for anybody looking at the project and making judgement calls off of it.

https://github.com/dyu/ffi-overhead/issues

I didn't do so because it wasn't my idea. I certainly don't mind though.

Reply on news.ycombinator.com