A viable alternative to go-ipfs? · Issue #1563 · ipfs/js-ipfs (original) (raw)

I would very much like for the js-ipfs implementation to be the most widely used IPFS implementation and I'm interested to know what the main blockers are for that.

We realise you have a choice of IPFS provider and your choice in important to us.

Or in other words, why do you type ipfs daemon and not jsipfs daemon?

I've had some interesting insight already:

@olizilla:
it's running on a different api port, so i have to config things to use it
i've got a repo in ~/.ipfs that has some things in i want to share
and the command is jsipfs rather than ipfs
these are all things to make it easier to dev both, but they all make me feel like the go one is the one i should be running day-to-day
also there is like 10 people on the js dht and 800+ on the go one

@lidel
this may be a niche reason, but there is an official docker image with go version as well
it may be important for devs, because historically, i used different docker images to quickly find regressions in IPFS APIs used by companion having one for jsipfs would be nice