not clear why to use this tool
over las 8 years I haven't seen much in Go except: 1) build binary; 2) copy to Docker.
or: 1) build inside docker directly with build image.
other things that kind of failed in Go ecosystem:
- Bazel. un-intelligible. very hacky for Go.
- GCP App Enginer "submit go code, it will fetch and build it automatically". kind of nobody is using that I know
- homebrew. not really failed, I see lots of people use it for go. but with
go install many people just self-compile and install from source code.
so recommend you:
- make couple bullet points why this is useful
- make elaborate (tables, slides, screenshots, benchmarks, etc.) comparing this tool to other tools (Bazel, Docker, Docker multi-staged, automatic GCP App Engine binaries form source, etc.). or whatever is relevant. if nothing is comparable, then say what those things are missing.
not clear why to use this tool
over las 8 years I haven't seen much in Go except: 1) build binary; 2) copy to Docker.
or: 1) build inside docker directly with build image.
other things that kind of failed in Go ecosystem:
go installmany people just self-compile and install from source code.so recommend you: