3 ms·

Surprised to not see mention of golang. Does anyone know if that's because even at Google scale, the simple "go build" command suffices?

by kzhahou 11y ago

varikin 11y ago
If I recall correctly, there was something about one of the main motivations in creating Go was to simplify build systems (partly reduce file reads of duplicate header files), so I imagine "go build" was designed to work at Google's scale. Also, apparently Bazel only contains like 10% of the build rules that Blaze has. Blaze being the internal version of Bazel. Some of those rules are Google specific, but I believe I read that some of them they would like to port (untangle from proprietary stuff) to Bazel, just haven't had the time to do so yet.
cap_theorem 11y ago
Go support is on the roadmap and is being tracked by this GitHub issue: https://github.com/bazelbuild/bazel/issues/79 https://github.com/bazelbuild/bazel/issues/79
adonovan 11y ago
(Former Blaze engineer and current Go tool builder here.) Blaze's support for building Go source code predates the existence of the 'go' tool and uses very different conventions for package naming, directory layout, testing, and project organization. As a result, most Google Go code cannot be built with 'go'. This can be a source of frustration at times.
- defen 11y ago
  Is "Blaze" something else or an autocorrect/typo of "Bazel" (topic of this post)?
  - qznc 11y ago
    Blaze is the Google-internal thing. Bazel is its Open Source clone.
  - e98cuenc 11y ago
    Blaze is the internal name of Bazel in Google (I don't know if both projects are identical, or if Blaze was just the "inspiration" for Bazel)
    - asuffield 11y ago
      They refer to distinct things but share a lot of their code. Blaze doesn't contain anything that you would find useful, you need our infrastructure for its other features to work.
  - activez 11y ago
    From the faq (http://bazel.io/faq.html http://bazel.io/faq.html): Did you rewrite your internal tool as open-source? Is it a fork? Bazel shares most of its code with the internal tool and its rules are used for millions of builds every day. What's up with the word "Blaze" in the codebase? This is an internal name for the tool. Please refer to Bazel as Bazel.

Surprised to not see mention of golang. Does anyone know if that's because even at Google scale, the simple "go build" command suffices?

by kzhahou 11y ago

Surprised to not see mention of golang. Does anyone know if that's because even at Google scale, the simple "go build" command suffices?

varikin 11y ago

If I recall correctly, there was something about one of the main motivations in creating Go was to simplify build systems (partly reduce file reads of duplicate header files), so I imagine "go build" was designed to work at Google's scale. Also, apparently Bazel only contains like 10% of the build rules that Blaze has. Blaze being the internal version of Bazel. Some of those rules are Google specific, but I believe I read that some of them they would like to port (untangle from proprietary stuff) to Bazel, just haven't had the time to do so yet.

cap_theorem 11y ago

Go support is on the roadmap and is being tracked by this GitHub issue: https://github.com/bazelbuild/bazel/issues/79 https://github.com/bazelbuild/bazel/issues/79

adonovan 11y ago

(Former Blaze engineer and current Go tool builder here.) Blaze's support for building Go source code predates the existence of the 'go' tool and uses very different conventions for package naming, directory layout, testing, and project organization. As a result, most Google Go code cannot be built with 'go'. This can be a source of frustration at times.

defen 11y ago
Is "Blaze" something else or an autocorrect/typo of "Bazel" (topic of this post)?
- qznc 11y ago
  Blaze is the Google-internal thing. Bazel is its Open Source clone.
- e98cuenc 11y ago
  Blaze is the internal name of Bazel in Google (I don't know if both projects are identical, or if Blaze was just the "inspiration" for Bazel)
  - asuffield 11y ago
    They refer to distinct things but share a lot of their code. Blaze doesn't contain anything that you would find useful, you need our infrastructure for its other features to work.
- activez 11y ago
  From the faq (http://bazel.io/faq.html http://bazel.io/faq.html): Did you rewrite your internal tool as open-source? Is it a fork? Bazel shares most of its code with the internal tool and its rules are used for millions of builds every day. What's up with the word "Blaze" in the codebase? This is an internal name for the tool. Please refer to Bazel as Bazel.