Forem: Piers Roberts

asdf ➡ mise

Piers Roberts — Wed, 24 Sep 2025 09:23:37 +0000

Switching from asdf to mise wasn’t just a fleeting developer whim - it’s the result of years of wrangling with version managers, misplaced shims, and dubious bash scripts. Mise, written in Rust, simply runs faster, feels smoother, and doesn’t make my shell configuration look like a post-apocalyptic cargo cult.

Why Change at All?

asdf had been the trusty sidekick for managing tool versions: Node, Python, Terraform, even that one VHDL project that only seemed to make sense very late at night years ago. It's polyglot, versatile, and compatible with nearly everything... except, apparently, my desire to not wait several seconds for basic operations. But as projects grew more sprawling, asdf’s reliance on shims and a sprawling ecosystem of shell-script plugins (some better maintained than others) started to wear thin. Mise sidesteps shims and instead hooks directly into the shell, updating the PATH with ruthless efficiency.

The Big Upsides

Speed: Mise eels punchy and modern.
Security: Instead of running unloved bash scripts from parts unknown, mise uses signed releases and curated registries.
Compatibility: Still supports the familiar .tool-versions file, so migration is painless. And if required, asdf plugins are a fallback, but only as a last resort.
DX (Developer Experience): Commands are simpler, and feel more natural and memorable. The UX feels like modern software, and less like an IRC bot.
Environment Setups: Injects environment variables with ease - it will set up env vars magically for you, I'm still on the fence with this, but I can see it's appeal.

The Trade-Offs

Mise won’t magically reuse your old asdf install directory, expect to reinstall some tool versions when switching. And while compatibility is high, the stated goal isn’t “100% asdf clone”, the focus is speed and security, not maintaining the entire asdf legacy ecosystem in amber.

Final Thoughts

The moment mise shaved a few precious seconds off my shell startup, I knew the time had come. It’s a classic story: Old friend asdf retires to a beach somewhere; mise takes over the shop, runs a tighter ship, and politely asks bash scripts not to track sand into the workspace. For polyglot projects and developers who value velocity and an ecosystem that’s alive and kicking, it’s a switch worth making.

Configure VSCode to preview Markdown files automatically

Piers Roberts — Mon, 22 Sep 2025 14:13:21 +0000

{
    "workbench.editorAssociations": {   
        "*.md": "vscode.markdown.preview.editor",
    }
}

hurl

Piers Roberts — Mon, 22 Sep 2025 14:11:57 +0000

Why I Use Hurl for HTTP API Testing

As a developer who often tests and experiments with APIs, I’m always on the lookout for simple yet powerful tools. Recently, I started using Hurl, and it’s quickly become one of my favorites for running and testing HTTP requests.

What I Like About Hurl

Hurl lets me write HTTP requests in plain text files, exactly how I would type them in a terminal or Postman, but with the added ability to automate sequences and handle variables. This means I can chain requests, grab OAuth tokens from one response, and use them in the next request — all without writing complicated scripts in another language.

It’s a command-line tool, which fits perfectly into my workflow and CI/CD pipelines. I appreciate that it’s lightweight, fast, and supports modern features like HTTP/2 and retries. The syntax is straightforward, so there’s almost no learning curve.

Some Quick Examples

Here’s a simple GET request I’ve used to fetch user data:

GET https://api.example.com/users
Accept: application/json

HTTP/1.1 200
[Asserts]
jsonpath "$.length()" > 0

And here’s how I retrieve an OAuth token and use it in another request:

POST https://auth.example.com/oauth/token
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials&client_id=YOUR_ID&client_secret=YOUR_SECRET

HTTP/1.1 200
jsonpath "$.access_token" != null
[Capture]
token = jsonpath("$.access_token")

GET https://api.example.com/data
Authorization: Bearer {{token}}

HTTP/1.1 200

How to Get Started

If you want to try it out, installing Hurl is easy with Homebrew:

brew install hurl

For more details and documentation, check out the official site: https://hurl.dev/

Final Thoughts

Hurl has simplified my API testing and automation work dramatically. If you want a no-fuss, scriptable way to run HTTP requests and manage OAuth tokens, give it a try — it might just save you a lot of time.