That's where the choice of Go (which I like as a language, mind you) has hamstrung them. Anyone who wants to do anything with it must either 1) add an entire se

That's where the choice of Go (which I like as a language, mind you) has hamstrung them. Anyone who wants to do anything with it must either 1) add an entire separate daemon as a requirement for their project/plugin/library/whatever, or 2) re-implement all of IPFS from scratch, and commit to tracking the reference Golang implementation forever. Sure they have a Javascript implementation they're developing in parallel, but in a world where most end user devices are battery powered what the hell good is that for anything serious or interesting? The requirement of a daemon to achieve reasonable network performance is already asking a lot of anything with a battery indicator. And at the same time the stability/reliability's still not there to use it for infrastructure, which is the other way they could have taken it (though they seem to stress that it's for end users). Again, just a very frustrating project to follow. Oh so close to being awesome. Maybe in another 6 months...