4 ms·
I don't know if that helps really. All you do in your comment is reiterate the issues and opine that they are not that bad. But they were bad enough for those s
by kova12 5y ago
I don't know if that helps really. All you do in your comment is reiterate the issues and opine that they are not that bad. But they were bad enough for those several times when I tried to use ipfs for my projects, and I am not a noob. There isn't any way some average user would get a value from this project.
I think a lot comes down to misrepresentation. When your product doesn't work, make it clear that it's a pre-alpha. When I see version 5.0 released, I expect to see something not just workable, but also mature and stable.
- hecturchi 5y agoLatest version of go-ipfs is v0.11.0, not v5.0. In any case, IPFS is not a "product", it is a number of protocols and layers sometimes used together and sometimes not (libp2p, ipld, kad-dht, gossipsub, bitswap, graphsync...). And all of them are in production and sucessfully used, but they also have different levels of maturity and evolve as we have the need and capacity. The fact that the state is not the final "interplanetary distributed rainbow that replaces the web as we know it" doesn't mean it is completely broken either.