Re:Gx: A package management tool built around IPFS
by noffle on Wednesday March 23, 2016 @03:59PM
(#11347702)
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.
> 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.
> 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.