Notices by Ayo (ayo@lonely.town)

Two boring releases! 🎉

ncdu 2.7: Adds support for transparent (de)compression when importing from or exporting to the JSON format, tilde expansion in the config file and some bug fixes.

ncdu 1.21: Backports the tilde expansion and some bug fixes.

https://dev.yorhel.nl/ncdu

@lanodan I'm pretty sure there's time manipulation magic involved.

I have a knack for buying products that have already passed their expiration date at the time I leave the store.

@Suiseiseki zig cc a.k.a. clang.

Compling ncurses with -fno-unwind-tables results in a static ncdu binary that's twice as large and crashes with "Illegal instruction".

I don't get it. :blobcatnotlikethis:

@lanodan @wolf480pl Yup, it ended up using rust-bin-1.79 as starting point.

@lanodan @wolf480pl Rather, they're now always using system-boostrap. Previously building a rust version from "source" involved an automatic download of some binaries to bootstrap it from, whereas now it requires a previous version to be already installed.

...and I only had 1.82 installed whereas apparently packages really wanted 1.81, so emerge insisted on bootstrapping from even earlier versions.

Yup, unmasking rust-bin did the trick. A few hours, 4 rust compiles and a million compilation warnings later and my system is up to date again. :blobcheer:

I'll... wait this one out. :blobcatnervous:

The nice thing about the humidity sensor in my bathroom is that it can reliably answer the question of when I last showered.

But that I have to look that up in Grafana in the first place might say something about my personal hygiene. :blobcatnotlikethis:

@wolf480pl Partly. I get a 2x speedup by disabling line buffering on STDOUT and another 200ms by disabling the path string construction.

Ncdu can convert the entire file to JSON in ~500ms, so there's clearly other inefficiencies left.

I wrote a tool that can walk through an ncdu binary export 4x slower than a non-parallel (cached) filesystem scan.

I wear a layer dog hairs on top of my clothes as a matter of fashion.

@lanodan Aye, and that doesn't even need a plugin. vim can do that with a `:set spell`.

The world is moving on to LLM-based code autocompletion, and here I am still coding in plain vim without any plugins. Too lazy to even setup ctags-based code navigation. :blobcattilt:

@andrewrk Will you start doing that with Github, too? Microsoft isn't any better...

I am continually baffled by the JS ecosystem. We already knew they can't decide on a single package manager, so there's multiple of them. Okay.

Apparently they're also incapable of writing stable software to the point that every project is now supposed to pin the version of the package manager they're using. Wat.

And to simply that mess, nodejs now ships with a package manager to manage the package managers.

Mastodon 4.3 requires Yarn 4.
Not in the Gentoo repos, great.
Website isn't looking too useful either. :blobcatfacepalm:

The good news: I survived another round of grocery shopping.
The bad news: I forgot to get some stuff again.

https://sourceforge.net/projects/ncdu.mirror/

lol.