<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nix on Unnamed Website</title><link>https://unnamed.website/tags/nix/</link><description>Recent content in Nix on Unnamed Website</description><generator>Hugo</generator><language>en-us</language><managingEditor>Anthony Wang</managingEditor><webMaster>Anthony Wang</webMaster><lastBuildDate>Tue, 09 Dec 2025 00:15:56 -0500</lastBuildDate><atom:link href="https://unnamed.website/tags/nix/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing Every NixOS Package</title><link>https://unnamed.website/posts/installing-every-nixos-package/</link><pubDate>Tue, 09 Dec 2025 00:15:56 -0500</pubDate><author>Anthony Wang</author><guid>https://unnamed.website/posts/installing-every-nixos-package/</guid><description>&lt;p&gt;Four years ago, I &lt;a href="https://unnamed.website/posts/installing-every-arch-package/"&gt;installed every Arch Linux package&lt;/a&gt; (and someone else tried the same crazy experiment with &lt;a href="https://www.naff.dev/blog/all-the-packages"&gt;Alpine Linux&lt;/a&gt;). But did I really accomplish my goal? Well&amp;hellip; I slightly cheated, since I only installed non-conflicting packages rather than literally every single Arch package. Besides, installing conflicting packages would overwrite one package&amp;rsquo;s files with the other&amp;rsquo;s, so they wouldn&amp;rsquo;t really both be installed.&lt;/p&gt;
&lt;p&gt;The solution, as with any Linux problem, is NixOS. With NixOS, conflicting packages or even multiple versions of the same package can coexist in the Nix store, which are then activated into your environment via symlinks, &lt;a href="https://xkcd.com/224/"&gt;hacked together with some nasty Bash and Perl scripts&lt;/a&gt;. Hooray for purely functional package management! Even better, &lt;a href="https://search.nixos.org/packages"&gt;search.nixos.org&lt;/a&gt; boasts a total of more than 120000 packages, nearly 10 times the measly 12232 packages that I installed in my Arch experiment.&lt;/p&gt;</description></item><item><title>RNG and Cosine in Nix</title><link>https://unnamed.website/posts/rng-cosine-nix/</link><pubDate>Sat, 12 Apr 2025 12:56:26 -0400</pubDate><author>Anthony Wang</author><guid>https://unnamed.website/posts/rng-cosine-nix/</guid><description>&lt;p&gt;NixOS is an immutable, atomic Linux distribution with a declarative and reproducible configuration and packaging system using the purely functional, lazily evaluated, dynamically typed Nix programming language.&lt;/p&gt;
&lt;style&gt;
.chardiv {
	float: left;
	width: 100px;
}
.charimg {
	height: 60px;
}
blockquote {
	min-height: 60px;
}
&lt;/style&gt;
&lt;div class="chardiv"&gt;
	&lt;img src="https://unnamed.website/img/char/kublai.png" class="charimg"&gt;
&lt;/div&gt;
&lt;blockquote&gt;&lt;strong&gt;Kublai&lt;/strong&gt;:
AAAAAAHHH too many buzzwords, what does that all mean???&lt;/blockquote&gt;

&lt;p&gt;Glad you asked! Basically, in NixOS, you can configure your entire system using a &lt;code&gt;configuration.nix&lt;/code&gt; file and NixOS will magically (using a bunch of Bash scripts) figure out what needs to be installed and how to do it. For instance, if you want to enable Firefox, you&amp;rsquo;d add &lt;code&gt;programs.firefox.enable = true;&lt;/code&gt; to your &lt;code&gt;configuration.nix&lt;/code&gt;. Easy as that.&lt;/p&gt;</description></item></channel></rss>