Why NodeJS & Browser JS, Typescript, Golang and Python over Rust? about aviondb HOT 4 OPEN

Thanks for the insights @aphelionz!

@vaultec81 You are right, I have used Golang for generating Android & iOS bindings. So, I think Golang & Rust can be 2 implementations that we can agree upon.

Should I add Golang & Rust to the README?

BTW, I added some details on the current state of go-orbit-db by Berty: #20

from aviondb.

Hi @ChristianKleineidam!

I totally agree with you. The plan to create GoLang & Python implementations (it is already available in different flavors of JS) was decided when the project started, and at that point in time, I didn't have much idea about the benefits of Rust.

But as I have learned it's better to have a Rust implementation than GoLang or Python. BTW, there are folks in the OrbitDB community (@aphelionz) who are already working on the Rust implementation.

So, I think we should change the README to reflect this. Any thoughts @vaultec81?

from aviondb.

I think we should definitely support Rust. I am a little wary of supporting python. Should we reconsider and only support JS, Golang and Rust? I think Golang has value as its used primarily in a lot of ipfs related areas.
Edit: I am not entirely sure on the specifics. I have heard of golang being compiled into Android and iOS bindings.

from aviondb.

An argument for JS in particular, one that we use for OrbitDB, is that JS is a very ubiquitous and accessible language, which means many more people can contribute meaningfully to the discussion and code base. Rust is more performant, uses fewer resources, etc etc - absolutely 100% yes, but the JS community is simply much much bigger at this point.

It's the same reason why we don't use Typescript, Lerna, Yarn, etc.

That all being said, @vasa-develop is right and you can check out http://github.com/rs-ipfs when you get a chance to see the latest Rust IPFS work :)

from aviondb.