|
You are here |
mill-build.org | ||
| | | | |
tmandry.gitlab.io
|
|
| | | | | At my company, we are moving our medium-sized C++ and Python codebase from CMake to Bazel. Moving to a new build system is a lot of work, so naturally, it has to be justified. Here are the benefits most important to us. First-class build system for C++ Our primary language today is C++, which doesn't have a standard build system. Bazel's C++ support is very good, and supports everything from code coverage reports to profile-guided optimization. | |
| | | | |
ashvardanian.com
|
|
| | | | | Experienced devs may want to skip the intro or jump immediately to the conclusions. The backbone of many foundational software systems - from compilers and interpreters to math libraries, operating systems, and database management systems - is often implemented in C and C++. These systems frequently offer Software Development Kits (SDKs) for high-level languages like Python, JavaScript, GoLang, C#, Java, and Rust, enabling broader accessibility. But there is a catch. | |
| | | | |
myme.no
|
|
| | | | | [AI summary] The article provides an in-depth exploration of using Nix as a package manager for development on NixOS, covering various programming languages and tools. It discusses challenges, best practices, and the power of reproducible builds with Nix. The author highlights the importance of Nix's concepts for managing software complexity and acknowledges the need for better documentation and discoverability in the Nix ecosystem. | |
| | | | |
www.chriswarbo.net
|
|
| | | [AI summary] A discussion thread clarifying misconceptions about state, the IO monad, and functional purity in Haskell by explaining how the language represents imperative programs as pure data structures. | ||