Explore >> Select a destination
|
You are here 
|
www.jeremykun.com | ||
| | | | |
filipnikolovski.com
|
|
| | | | | A blog about programming, technology and open-source stuff. | |
| | | | |
enoent.fr
|
|
| | | | | Random musings of a software engineer. | |
| | | | |
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. | |
| | | | |
blog.nuculabs.de
|
|
| | | Hello, In this article I will introduce you to pyenv, a tool for managing python environments. Installing pyenv is pretty straight forward, you'll need to clone the repo and add the binaries to the path. For a typical Debian based distro using the Zsh shell the instructions would be: 1 2 3 4 git clone https://github.com/pyenv/pyenv.git ~/.pyenv echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.zshrc echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.zshrc Then, in order for this to take effect, you need to reload the shell with: source ~/.zshrc, or just restart your terminal. ?? | ||
