pkgx VS white-paper

I’m liking pkgx over asdf as it can activate project tooling upon cd’ing into a project folder.

https://pkgx.sh

I saw some alternatives being suggested and wanted to do the same (Also, so that I can look back at this item, through my comments :) ). Started using https://pkgx.sh/ lately. I know it has some baggage with tea.xyz and crypto, but it is also easy to get started with.

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).

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:

1. pkgx

Before diving in, it's a good idea to have a package manager handy, like tea. It'll handle your development environment and simplify your life!

Direct fast-track link to repo

checkout https://github.com/teaxyz/cli and https://github.com/teaxyz/pantry

Install is tea: sh <(curl https://tea.xyz) and

Not even just gas fees -- the publishers have to outright pay to get a package added:

> Specifically, the package maintainer must:

> [...] Contribute to the package’s reputation and trustworthiness by steeping tea tokens.

https://github.com/teaxyz/white-paper/blob/main/white-paper....