Yet another binary embedder

<p>Hi, I wrote a new code gen tool for embedding binary assets, called <a href="https://github.com/lmas/yaber">yaber</a>.</p> <p>It&#39;s a yet another tool (heh) that tries to be minimalistic, simple to use and guess sane defaults, aswell as producing gofmt&#39;ed (and go:generate) code and a accompanying test file.</p> <p>I&#39;m currently trying it in production for a couple of my own projects, but I&#39;m looking for inputs/criticism/testing from others. Is it a worthy competitor to <a href="https://github.com/avelino/awesome-go#resource-embedding">similar tools</a>?</p> <hr/>**评论：**<br/><br/>bear1728: <pre><p>I like your <code>getPackageName</code> function! It looks simpler than what I hacked together for <a href="https://github.com/tscholl2/embd" rel="nofollow">my own binary embedder</a>. Also great name :)</p></pre>karnd01: <pre><p>Nice Work! Looks like a great start.</p> <p>just some things that may be a nice-to-have that I tried to address in <a href="https://github.com/go-playground/statics" rel="nofollow">statics</a>:</p> <ul> <li>Maybe an option to decompress files on startup or store decompressed version after first decompression to avoid doing it multiple times ( would speed up serving of files from http.FileServer )</li> <li>Support Symlinks. It&#39;s not fun but whenever I embed it&#39;s mostly my html assets javascript, css and images which a good deal of the time I need symlink folders for images etc. embedded in a CSS library.</li> <li>Support for generating multiple static files within the same package eg. statically embed html assets and website certificates, where the folders happen to be at the same level in the same package. The reason I would not want to put in the same folder is when adding static files to http.FileServer I can have my sites cert files exposed.</li> <li>Possibility to embed the generation command right inside the generated file using go:generate for easy of automated builds.</li> </ul> <p>Feel free to steal anything from my package that may help and keep up the great work :)</p></pre>kylewolfe: <pre><blockquote> <p>Maybe an option to decompress files on startup or store decompressed version after first decompression to avoid doing it multiple times ( would speed up serving of files from http.FileServer )</p> </blockquote> <p>Given the amount of use cases for embedded assets, and each having it&#39;s own best practice for caching of the assets, I&#39;d say it&#39;s fine to leave this feature out.</p></pre>