There are quite a few options for binary data with go, I imagine people will converge on one eventually, however I don't see any harm in a few different people trying out different options. For this kind of tool I wouldn't want to bother with two packages, I'd rather just import one package and be done with it. Have you used any of these packages? I'm planning picking one at some point for this and other projects as it'd be nice to wrap the templates used into the binary and not have to bother uploading them separately.
No I haven't, it was more out of curiosity. Bindata is the obvious prior art in this case so it would be interesting to get an idea in how these overlap and differ.
Unfortunately though assetfs seems to be under development bindata itself hasn't been updated since 2015 and there are now numerous issues and PRs pending so it's nice to have an alternative.
Does this do anything different from go-bindata paired with go-bindata-assetfs?
There are quite a few options for binary data with go, I imagine people will converge on one eventually, however I don't see any harm in a few different people trying out different options. For this kind of tool I wouldn't want to bother with two packages, I'd rather just import one package and be done with it. Have you used any of these packages? I'm planning picking one at some point for this and other projects as it'd be nice to wrap the templates used into the binary and not have to bother uploading them separately.
No I haven't, it was more out of curiosity. Bindata is the obvious prior art in this case so it would be interesting to get an idea in how these overlap and differ.
Unfortunately though assetfs seems to be under development bindata itself hasn't been updated since 2015 and there are now numerous issues and PRs pending so it's nice to have an alternative.