Explore >> Select a destination
|
You are here 
|
www.jeremykun.com | ||
| | | | |
jmmv.dev
|
|
| | | | | This is a rare post because I don't usually talk about Google stuff here, and this post is about Bazel: a tool recently published by Google. Why? Because I love its internal counterpart, Blaze, and believe that Bazel has the potential to be one of the best build tools if it is not already. However, Bazel currently has some shortcomings to cater to a certain kind of important projects in the open source ecosystem: the projects that form the foundation of open source operating systems. This post is, exclusively, about this kind of project. | |
| | | | |
filipnikolovski.com
|
|
| | | | | A blog about programming, technology and open-source stuff. | |
| | | | |
mill-build.org
|
|
| | | | | [AI summary] The blog post explores the inner workings of modern build tools, emphasizing their use of a build graph to manage tasks efficiently. It compares tools like Bazel, Gradle, and Mill, highlighting how each defines and processes the build graph. The post explains caching, parallelism, and the importance of a structured build graph in optimizing build processes. It also discusses the advantages of using a programming language for defining build configurations, such as better IDE support, compiler assistance, and access to a rich library ecosystem. The conclusion underscores that while build tools may appear different on the surface, they share a common goal of enhancing development efficiency through automation and optimization. | |
| | | | |
matthewrocklin.com
|
|
| | | |||
