4 ms·
In theory, yes. In practice... you will need to either a) force everyone in your team to never use native Go tools ever, or b) cobble together third-party tools
by zapita 7y ago
In theory, yes. In practice... you will need to either a) force everyone in your team to never use native Go tools ever, or b) cobble together third-party tools to bridge the two worlds. Start with https://github.com/bazelbuild/bazel-gazelle https://github.com/bazelbuild/bazel-gazelle and see how deep the rabbit hole goes.
It's possible, but it's not trivial, and not nearly as smooth as using the Go tools in the first place. Unless you have a hair-on-fire problem dealing with cross-language dependencies or insanely long build times, it will probably not be a good use of your time.
- habitue 7y agoYeah, I think the heuristic should be "Am I forced to migrate to bazel to solve real problems my company is having?" Vs. "Can I migrate because bazel is the new thing"