Bazel is much easier to express dependencies with, especially cross-directory
dependencies. As we are moving to a Go-based implementation, it will be much
easier to ensure correctness of implementation via Bazel than via complex
Makefiles.
This also means we can remove 1 Linux build and 1 macOS build on Travis, so
hopefully, this will also speed up our CI execution, as the macOS builds seem to
sequential, rather than parallelized, and don't buy us anything extra, except
testing two different build/test systems.
Bazel is much easier to express dependencies with, especially cross-directory dependencies. As we are moving to a Go-based implementation, it will be much easier to ensure correctness of implementation via Bazel than via complex Makefiles.
This also means we can remove 1 Linux build and 1 macOS build on Travis, so hopefully, this will also speed up our CI execution, as the macOS builds seem to sequential, rather than parallelized, and don't buy us anything extra, except testing two different build/test systems.