Google Releases Bazel 1.0 Build System With Faster Build Performance

[phoronix]

Phoronix: Google Releases Bazel 1.0 Build System With Faster Build Performance

Google open-sourced their Bazel build system four years ago while today it reached version 1.0 for this multi-language, multi-platform build solution...

http://www.phoronix.com/scan.php?page=news_item&px=Google-Bazel-1.0-Released

[pal666]

lol, fast and java in same sentence

[RahulSundaram]

lol, fast and java in same sentence

Fast is relative of course but OpenJDK JVM is a pretty mature high performance implementation

[bug77]

lol, fast and java in same sentence

Two words for you: GraalVM

[smartalgorithm]

someone is stealing my justification for longer coffee breaks...

[tildearrow]

Two words for you: GraalVM

Nice! Is it possible to use this to directly speed up .jar execution?

[kpedersen]

Looking into it, I much prefer CMake. However one area that CMake doesn't seem to handle well is the NDK cross compilers. CMake with gradle is horrible (because Gradle is horrible). However Bazel seems to be able to do the C++ and Java Activity boilerplate without requiring additional cruft and so looks quite elegant.

https://docs.bazel.build/versions/master/android-ndk.html

[bug77]

Nice! Is it possible to use this to directly speed up .jar execution?

Considering one of its features is AoT compilation (aka translation of jars to executables), not only will it speed up execution, but it will cut the memory consumption while at it. I'm not sure where it's at right now, last I checked it only worked on 64bit Linux executables. Which is good enough for me, but not good enough for production

[euler271]

lol, fast and java in same sentence

probably meant, faster than python(meson), which to be fair, almost everything is. If it werent for it's ninja backend, meson would be totally useless.

[Almindor]

Bazel is actually quite good for multi-system builds. Most people won't "get it" because it's not aimed as a direct replacement for Make, Cmake or the other traditional builders.

Bazel is one layer above. It's used to build source -> binaries sure but also to build binaries -> artifacts and artifacts -> deployables (e.g. deployment step functions). This is a huge unifying and performance boon for people/companies utilizing the cloud heavily. The hermeciticy and highly efficient caching ensures it's better than most others you could've cooked up for your pipeline.