Farid Zakaria’s Blog

Warning If you are pissed off reading this, you can start here and work your way back.

tl;dr; omnibin is a FUSE filesystem that puts every binary nixpkgs ever shipped on your $PATH.

We are right around the corner from NixCon 2026.

tl;dr seenix.dev lays every byte of a Nix closure out on a map, one pixel per byte, and lets you zoom from a whole NixOS system down to the hex of libc.so.6.

“Curiosity is only vanity.

While building trynix I needed somewhere to host a store-path that did not exist on cache.nixos.org.1 I wanted to demonstrate that non-Nixpkgs store paths could be booted just as easily.

tl;dr; trynix-preview is a GitHub action that comments a link on a pull request which lets you boot the PR’s build in the browser using https://trynix.dev.

tl;dr Try it at https://trynix.dev.

After the last post introduced the holy grail of version ranges for nixpkgs, @arianvp over X felt it was a doomed endeavor: “What happens when a plan spans revisions and you accidentally load two versions of the same library?

Update You can try this live at fzakaria.github.io/grail and query nixpkgs version ranges in your browser, the same solver, compiled to WebAssembly.

I recently wrote about omniflake, accessible via https://omniflake.com, which indexes over 12,000 flakes and makes them available through a single flake input.

Flakes are undoubtedly here to stay, and I’ve made my opinion on them well-known: they are “meh”.

This is a fun little trick I came across at $DAYJOB.

I was pleasantly surprised and happy to see that my article ‘Your executable is a SQLite database’ resonated with people.

I have been probably obsessed with two things in the last few years: Nix as a tool to explore innovative ideas that require the capability to rebuild the world and replacing ELF with SQLite as an executable format.

The core of nixpkgs-multiverse, when you strip away the Nix API and the CLI, is an index.