Add remote compilation to bloop #673
Hello, @kaishh. Remote compilation is a feature we're interested in. Architecturally speaking, bloop was built to support remote compilation from the start and ensure that compilations of the same project do not run into each other.
To support remote compilation, we want to implement Bazel's remote compilation protocol (https://github.com/bazelbuild/remote-apis) because it seems it's being implemented by major build tools, and it's becoming an standard.
However, it's not a priority and there will be no activity on remote compilation in the next three months at least. I want to make sure that local development is as fast as it can get with bloop before jumping to cover another use case.
I'll reopen this ticket when I consider bloop ready to take on this challenge. It's still not clear to me I want to include remote compilation in the scope of bloop. IMO, any tool that wants remote compilation can implement it outside of bloop and that flexibility might be even better as the design space to implement remote compilation is too big and there are many trade-offs involved.