I do a lot of static compilation.
I generally prefer smaller, simpler stuff.
I only started using Linux recently. Until then I used NetBSD, and their libc is much nicer I think. Static compilation is of course no problem on NetBSD.
NB. These are four points that apply to me, but not necessarily to anyone else, i.e., 1. the distribution I use, 2. what I like to do, i.e., compile static binaries, 3. particular personal preferences, i.e., minimalism, limitation that forces creativity, and 4. I did not switch from glibc to musl, I switched from NetBSD libc to musl.
It's also fun when stuff occasionally does not compile in that it forces me to learn about certain differences between musl and glibc and usually I learn something I did not know about C or the compilers.
I'm not the only person in the world who prefers musl. For example,
https://raw.githubusercontent.com/hardbol/spitbol/master/rea...
When this happens, one can split access.log into pieces, process separately then recombine.
But that's more or less what sort(1) does with large files, creating temporary files in $TMPDIR or other user-specified directory after -T if using GNU sort.
There was a way to eliminate duplicate lines from an unordered list using k/q, without using temporary files but I stopped using it after Kx, Inc. was sold off and I started using musl exclusively. q requires glibc.
For example, something like
Can this be done in ngn k.The other approach I use to avoid temporary files is to just put the list in an SQL database, add a UNIQUE constraint, and update the database.