It's possibly not clear how this picture is. There is a structure like this
3-> [node][python][java]... Almost any language
2-> FFI Layer (essentially a "c" interface)
1-> Rust (safe_client libs)
1-> rust apps can use the rust layer directly.
2-> FFI (foreign function interface) really only exposes a "c" interface which allows "native" libraries for a lot of languages to "import" into other programming languages
3-> Libraries already prepared and packaged for other languages. We only have node at this time, but nothing stopping us having java python lua etc. (except time)
Our goal here is to do similar with this as other projects do and as we are trying to do with our "demo" apps or example code snippets (we struggle with the demo app name a lot) and have community maintained native bindings. I suspect we may end up as maidsafe having node/python/java libraries and have these built and deployed via our CI scripts. It's a debate in house though (rightly) as to how much we take devs off launch to do this right now.
Hope this helps a bit anyway.