3 ms·

I'm wondering if the goal of this porting project would've been achieved by Java's newly gained native/AOT compilation feature. Probably not, as a huge Java .so

I'm wondering if the goal of this porting project would've been achieved by Java's newly gained native/AOT compilation feature. Probably not, as a huge Java .so brings the JVM's infrastructure for gc etc., and too much overhead. Still, I hope we can get rid of the language-centric ecosystems we have in favour of established OS/POSIX ways for shared libs, or an evolution thereof.

kjksf 8y ago
There are an estimated 1 million of Go programmers. The goal of the project was to enable those Go programmers to be able to use RavenDB database in projects written in Go. The company also maintains Python client library and Node.js client library. It's not about Go vs. Java as a technology but enabling as many programmers as possible to use RavenDB.
- tannhaeuser 8y ago
  I understand the goal, and my comment wasn't so much arguing in favour of one language vs another, but rather that developing the same thing for multiple languages over and over seems wasteful.
  - Matthias247 8y ago
    In those client things the amount of the code that can be moved into a cross-language shared library might be lower than expected. E.g. the wire protocol and socket handling might be an option - but it's often not that big. The bigger part might be transformation of the programming languages types into something useful for the client (e.g. through serialization), which has be be redone anyway for each language. And after that the question comes up whether sharing the remaining things yields enough benefits to justify the hassle of having a dependency which is less portable, requires another build system, etc. That's my general experience with those kinds of projects - I don't know enough about RavenDB in particular to tell if it's the same here.
yxhuvud 8y ago
Looking at the way the wind blows it rather is towards more language centric ecosystems, than towards less of it. That said I'm still waiting for when the language ecosystems start to standardize how they interact with each other. That is a very hard nut to solve, but it would also be a quantum leap forward.
pjmlp 8y ago
> Java's newly gained native/AOT compilation feature A feature that exists since around the mid-2000's. It was only missing from the gratis version of Java, the large majority of commercial JVMs always had AOT support.

kjksf 8y ago

There are an estimated 1 million of Go programmers. The goal of the project was to enable those Go programmers to be able to use RavenDB database in projects written in Go. The company also maintains Python client library and Node.js client library. It's not about Go vs. Java as a technology but enabling as many programmers as possible to use RavenDB.

tannhaeuser 8y ago
I understand the goal, and my comment wasn't so much arguing in favour of one language vs another, but rather that developing the same thing for multiple languages over and over seems wasteful.
- Matthias247 8y ago
  In those client things the amount of the code that can be moved into a cross-language shared library might be lower than expected. E.g. the wire protocol and socket handling might be an option - but it's often not that big. The bigger part might be transformation of the programming languages types into something useful for the client (e.g. through serialization), which has be be redone anyway for each language. And after that the question comes up whether sharing the remaining things yields enough benefits to justify the hassle of having a dependency which is less portable, requires another build system, etc. That's my general experience with those kinds of projects - I don't know enough about RavenDB in particular to tell if it's the same here.

yxhuvud 8y ago

Looking at the way the wind blows it rather is towards more language centric ecosystems, than towards less of it. That said I'm still waiting for when the language ecosystems start to standardize how they interact with each other. That is a very hard nut to solve, but it would also be a quantum leap forward.

pjmlp 8y ago

> Java's newly gained native/AOT compilation feature A feature that exists since around the mid-2000's. It was only missing from the gratis version of Java, the large majority of commercial JVMs always had AOT support.