|
You are here |
jmmv.dev | ||
| | | | |
blog.bazel.build
|
|
| | | | | [AI summary] The Bazel Blog announces an experimental feature in version 0.25 that significantly reduces network bandwidth usage in remote builds by virtualizing action outputs and downloading only metadata instead of full file contents. | |
| | | | |
enoent.fr
|
|
| | | | | Random musings of a software engineer. | |
| | | | |
blog.sumtypeofway.com
|
|
| | | | | [AI summary] The author discusses the transition from Cabal to Bazel and rules_haskell for managing a large Haskell project, highlighting the benefits of Bazel's explicit dependency management, caching, and tooling, while addressing the challenges of long CI build times and the ethical implications of resource consumption. | |
| | | | |
smyachenkov.com
|
|
| | | Kotlin did an amazing job saving and including into its scope most of all valuable Java libraries, frameworks, and tools. But there is one type of tool that can't be easily imported and reused - static code analyzers. Java developers have implemented a lot of tools for code analysis, therefore, if you have worked with Java you might be familiar with some of the following projects: PMD, checkstyle, findbugs, spotbugs, etc. | ||