4 ms·
I don't know if IPFS enthusiasm has waned, I see a lot of excitement, but the real problem on the web is that browser support (outside Brave) is non-existent.
by pimterry 5y ago
I don't know if IPFS enthusiasm has waned, I see a lot of excitement, but the real problem on the web is that browser support (outside Brave) is non-existent.
If users can't use it, there's not much point in trying to build for it. There are IPFS gateways that try to provide IPFS via HTTP, but they don't seem to be popular, I think there's some fundamental challenges there that make them the worst of both worlds.
- ftyers 5y agoAn additional problem is the lack of language bindings/implementations. There is no fully-fledged implementation apart from the Go one, which makes getting many developers onboard a challenge.
- Turing_Machine 5y agoThe JS implementation is pretty feature-complete, though still classed as experimental/alpha. https://js.ipfs.io/ https://js.ipfs.io/
- ftyers 5y agoYeah, which is a good step forward, but it's definitely not usable yet in my experience. There is definitely a vibe of "why would anyone want to use anything other than Go" in the community. (I actually really like IPFS, I just wish that it fitted into the standard Unix Dec environment a bit better).