flizzo

A couple months ago I lobbied for (and won) my weekly trivia team to use the name "mike's hard lemonparty"

Then I learned exactly how old I was

You're right, Borkfan is too easy to remember, my not-ban fork is now called Frabnok.

Look out, professional Nix crybaby Jon Ringer is back with his fork.

In other news, I have my own as well called Borkfan, absolutely not a ban fork due to my having threatened multiple people, but instead dedicated to the idea that a technology that lacks chud approval must necessarily not be in the true hacker spirit.

Orange site on pager bombs in Lebanon:

If we try to do what we are best at here at HN, let’s focus the discussion on the technical aspects of it.

It immediately reminded me of Stuxnet, which also from a technical perspective was quite interesting.

Yup I refused to even post that nonsense because I did the exact same scroll through it and was nonplussed by the amount of preamble this dude absolutely did not merit in defense of his terminal poaster syndrome.

So the orange site is having a normal one over Python BFDL trying to skirt CoC by talking about mod actions against some old dude who caught a suspension for being precisely the sort of edgelord poaster I'd expect out of a Python maintainer, which the orange site was also not happy about. I even read a bunch of his posts in the thread, like where he calls people standing up to NixOS leadership "true villains".

Pauly G is telling on himself here: what he means is that his kids learned English from movies.

I've been out-of-the-loop for a bit on the Nix drama. Is there a good summary of the last couple weeks?

This is my favorite thing to do.

This post has "everything" in the same way as the buffet of the Beau Rivage at midnight: the goods are warmed over, but the overs are good warm.

the odd sobriquet of Auxolotl

Has the pendulum swung back already? I make it to parenthood just in time for puns to fall out of favor?

Now that Dr Dolstra has gone

Dr Dolstra

This particular curmudgeon, though, feels that this particular Nix fork missed a big opportunity: to automatically generate and manage more human-readable filesystems.

The cardinal sin of Nix is apparently naming things. Since Aux exists for any other reason than fixing this, it has not atoned and can never atone.

Nix works wonders by automatically storing code in a software-generated and software-managed directory hierarchy. This has a profoundly off-putting side-effect: it eliminates a human-readable filesystem.

A specter is haunting Linux - the specter of /nix/store.

This particular jaded old hack much prefers the approach of GoboLinux.

And what is the solution? ~~FreeBSD Ports~~GoboLinux!

What Gobo offers is akin to semantic versioning, but applied to the filesystem: a semantic filesystem layout, where folder names encapsulate versioning info and are more meaningful than the old 1970s reduce-typing-effort-at-all-costs approach.

Cool, semantic versioning, that will save us.

The thing is, though, that we were all beginners once, and anything that makes Unix even more forbidding for both beginners and veterans is a problem.

The last great addition to Linux was FHS 2.3, apparently.

I don't want to give this more oxygen than it deserves by making a separate post, but Jon Ringer has finally exhausted Reddit.

I honestly think the big win coming out of the most recent events is framing https://github.com/nixos/nix as "CppNix". There are lots of good explanations about how each of the pieces relates to one another, but for practical purposes, many of those pieces live in one place, and now we can all call that place CppNix, which sounds...less than ideal! I think it's the thing that will make clear just how dependent the whole enterprise is on that piece, and just how tightly that piece is controlled, even if other people on the CppNix team think that something like a fork is overkill and that things are better, because they can only be so good when CppNix is the default for a bunch of things it shouldn't be. Some of those other team members have been working to make that less true, and I think that's great, but I think a lot of recent documentation improvements have managed to hide the tight coupling, even if it wasn't intentional, and this makes it absolutely clear.