Don't think so, I think most tools out there have the same basic premise behind embedding assets. I think it would be great to have one standard tool into the stdlib. Since Go is a language for the web this would align greatly with something like this.
On Monday, April 30, 2018 at 1:09:02 PM UTC-5, Ian Lance Taylor wrote: > > On Mon, Apr 30, 2018 at 7:03 AM, John Unland <unlan...@gmail.com > <javascript:>> wrote: > > > > Hey everyone I've been mulling over this for a couple of days, thought I > > would get some feed back on the possibility of shooting a proposal to > have > > embedding static assets into the stdlib. From the looks of it this > wouldn't > > break Go 1 compatibility thou I'm wondering if it would be better to > just > > have this apart of a Go 2 release instead. > > > > Any thoughts? > > How would this differ from something like > https://github.com/rakyll/statik , which I think could be invoked via > go:generate? > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
