News for hackers. Stuff that matters.

A comment on Bazel 1.0. Parent comment

Re:Bazel 1.0 by jxramos on Friday October 18, 2019 @04:21AM (#21289559)
Aren't the hot compilers kept around under this mechanism to speed up the next incremental build round? I think it's not just caching of intermediate build output but also not letting the tools start from a cold start.
[ Parent | on HN ]
Re:Bazel 1.0 by paulddraper on Monday October 21, 2019 @02:32PM (#21315621)
Yes, and I included that in my point. Certain compilers: Java, Swift, TypeScript are faster with long-running worker processes.

To be fair, that doesn't require a long-running Bazel process to manage them, but that does become a natural choice.

[ Parent | on HN ]