3 ms·
I completely support the IPFS (especially with them keeping content hosting explicitly out of scope). The problem I faced when trying to leverage IPFS for a pro
by jumperjake 11y ago
I completely support the IPFS (especially with them keeping content hosting explicitly out of scope). The problem I faced when trying to leverage IPFS for a project is that the reference implementation is very difficult to use in languages other than Go, and to completely embed in applications (as in staticly linking to sqlite).
- joeyspn 11y agoI guess it just needs time for maturing: more languages and better UX. If IPFS finally piggybacks on the Ethereum ecosystem it will accelerate considerably this...
- ashark 11y agoYeah, I like Go, but the reference implementation should have been a C library (or similar). There are splinter projects trying to implement it for other languages, but they're either already dead or moving at a snail's pace. I love the idea, but that decision leaves me with little confidence that it'll catch on.