nix
asdf
Our great sponsors
nix | asdf | |
---|---|---|
370 | 339 | |
10,814 | 20,393 | |
6.1% | 2.6% | |
10.0 | 7.9 | |
2 days ago | 5 days ago | |
C++ | Shell | |
GNU Lesser General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nix
-
Tvix – A New Implementation of Nix
(Nix itself is slowly chugging along with Windows via MinGW - https://discourse.nixos.org/t/nix-on-windows/1113/108 and https://github.com/NixOS/nix/issues/1320 , for example.)
-
Colima k8s nix setup
Nix is a cross-platform package manager. It uses the nix programming language. Nix and NixOs are often used in the same context, but while the first is a package manager, the latter is a linux distribution based on nix.
-
NixOs - Your portable dev enviroment
Today I want to talk to you about Nixos. What is it? Nixos is a declarative and reproducible OS, partly taking the words used on their own page. What does that mean?
-
Nix – A One Pager
Software developers often want to customize:
1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).
2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.
3. or even their operating systems: for development, for CI, for deployment, or for personal use.
Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):
- reproducible: what works on your dev machine also works in CI in prod,
- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,
- reliable: all changes are atomic with easy roll back.
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Ask HN: Could Nix make crypto mining more efficient?
- it reduces bloat, because you can generate an environment or OS image with only the software needed to run a specific program or service
My guess is that a big efficiency gain would come from the second point, because you don't waste CPU on code that you don't use.
Does this make sense? Has anyone explored this?
[0]: https://nixos.org
-
Go + Hypermedia - A Learning Journey (Part 1)
1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity
-
Nixing Technological Lock In
"Your greatest challenge lies ahead -- and downwards..."
Oh, wait a second, my bad, that's the quote on the box cover for Zork I: (
https://upload.wikimedia.org/wikipedia/en/a/ac/Zork_I_box_ar...
https://en.wikipedia.org/wiki/Zork
)
What you really wanted was a link to where you could download Nix/NixOS -- and/or learn more about it!
Here ya go!
"Your greatest challenge lies ahead -- and downwards..."
:-) :-)
I say all of the above in the spirit of humor -- and as a NixOS user and fan!
(But yes, there is a learning curve to it, so yes, learning Nix/NixOS could be a challenge!)
((But you're a bright person, you have Google and ChatGPT to assist you, and you like challenges!))
-
What it was like working for Gitlab
Semi-related, I would recommend to anyone who is a Linux native to try to find some kind of "minimum viable setup" that is really really easy for you to run out of VirtualBox or Parallels or something for this reason. No matter where you go, you know you can have a suite of tools which work just as you want them to there. Being able to tear it down and rebuild it quickly is also a great way to deal with debugging certain kinds of problems of the "it runs/doesn't run on my machine" category.
How you do this is of course up to you. At one end of the spectrum is just relying on your memory. At the other end is using NixOS https://nixos.org/ to get fully reproducible builds anywhere you go. Between these are a vast field of options. I know a guy who maintains an Ansible file set to `host: localhost` which installs everything he wants from that file. For me, I just stick with the latest Ubuntu version and maintain a few shell scripts [1] that install 80% of what I like to have on a new install.
If you like the scientific approach, you can install something like https://atuin.sh/ and do some statistics on what programs you actually run most frequently based on your long term shell history.
-
Cloudflare R2-Backed Nix Binary Cache on Fly.io
See https://github.com/NixOS/hydra/issues/838 for making content-addressed derivations supported by hydra.nixos.org. At that point, we can actually try out the XP feature at scale.
Also see https://github.com/NixOS/nix/issues/8919 for this accepted RFC
Once those things are done, we can get back to merging in the IPFS code.
Now that there is an Nix team and I am on it, there is much, much less of an issue of these experiments being caught in limbo :).
asdf
-
Volta – Fastest Node version manager in Rust
Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions
-
Pyenv – lets you easily switch between multiple versions of Python
Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?
These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…
We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.
-
A Journey to Find an Ultimate Development Environment
The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).
-
How to Install Your Python Version on Ubuntu
(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.
-
Beginners Intro to Trunk Based Development
Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).
-
Practical Guide to Trunk Based Development
There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:
- Criando seu ambiente com ASDF
-
Kotlin version manager
I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.
-
How do i keep my "devops tool" always up to date in a smart way ?
I use the asdf version manager.
-
Fish – Update on the Rust Port
You might check out rtx[1]
Its an asdf[2] rewrite, in rust, that can do most of the things nvm can
What are some alternatives?
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
SDKMan - The SDKMAN! Command Line Interface
void-packages - The Void source packages collection
pyenv - Simple Python version management
flatpak - Linux application sandboxing and distribution framework
rbenv - Manage your app's Ruby environment
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
guix - Read-only mirror of GNU Guix — pull requests are ignored, see https://guix.gnu.org/en/manual/en/guix.html#Submitting-Patches instead
volta - Volta: JS Toolchains as Code. ⚡
NixOS-docker - DEPRECATED! Dockerfiles to package Nix in a minimal docker container
HomeBrew - 🍺 The missing package manager for macOS (or Linux)