noffle

Excellent work; gorgeous website! Congratulations on the release.

There's also a (very WIP) "IPFS Textbook": https://github.com/RichardLitt/ipfs-textbook/

Excellent concerns! gx addresses both:

> Let's say we adopt this. Cut to some small number of years in the future, and everyone is complaining about how dealing with 46-character-long opaque strings is terrible.

Agreed. You can point gx to "repos" (/ipfs addresses that map (package, version) => /ipfs/... addresses. This lets you use simple names, and anyone can publish a repo.

see https://github.com/whyrusleeping/gx#repos

> This is a great idea, but there's no mention of versioning. As a long-time advocate of what we now refer to as Semantic Versioning, I can't help but see this as a disaster waiting to happen.

Sorry, this is a documentation failure rather than a feature failure: gx has semver built in and adheres to it today.

gx is a language-agnostic, distributed package manager. It uses IPFS for package retrieval and publishing, and git-like hooks for per-language/ecosystem implementations (like Go: https://github.com/whyrusleeping/gx-go).

gx is a generic package manager on top of IPFS that uses git-style hooks for adding per-language support. It's already being used to manage dependencies on the go-ipfs project: https://github.com/whyrusleeping/gx

Bonus: there's also a IPFS git remote implementation! https://github.com/cryptix/git-remote-ipfs

There are a lot of possible ways to approach this, such as overlay networks where peers interested in a topic can learn of and publish updates quickly to others (e.g. pubsub).

IPFS needs not be a kitchen sink: it's very easy to layer entirely application-layer overlay networks that do other useful things.

The "FS" part of IPFS can be misleading: you can store arbitrary data in IPFS.

The tooling merely provides a means of viewing Merkle DAGs (the base data structure) as a file hierarchy because it's a pretty clean 1:1 mapping that's familiar to many people.

My in-dev game thing (http://www.aliengrit.com) shares game logic code across the client and its Node server. If you've cleanly separated rendering logic from game logic for all game entities, it works really well. (i.e. the server just runs the same code without the graphics bit attached).

The astute reader will also note that Five and Six were also not discussed. From the fourth paragraph, "I will be discussing a subset of the nine challenges".