That’s not an affiliate link that’s an anonymous tracking link.

These suggestions are essentially the same as other privacy and libre focused recommendations.

Ente is a beautiful, private cloud for your memories, with apps for mobile, desktop and web.

At Ente, we use Local AI to deliver features like face recognition and magic search, while respecting the privacy of your photos.

We’ll now join a cohort of builders pushing technology forward for an AI that is light, private and accessible.

There seems to be mixed reactions to this suggestion. I don’t know enough to understand why.

Awesome! Best of luck to the new team!

How well NixOS and Nixpkgs are maintained absolutely affects users of NixOS. This may have just saved NixOS from becoming an unmaintained or at best slowly maintained project that people advise against using for anything serious.

I think that Nix flakes have some considerable benefits, such as:

Convenient pinning of evaluation-time dependencies

Eliminating pointless rebuilds of code by only including tracked files in builds

Making Nix code, on average, much more reproducible by pervasive pinning

Allegedly caching evaluation

Possibly making Nix easier to learn by reducing the amount of poking at strange attribute sets and general NIX_PATH brokenness

However, at the same time, there are a few things that one might be led to think about flakes that are not the most effective way of doing things. I personally use flakes relatively extensively in my own work, but there are several ways I use them that are not standard, with reason.

Flakes are optional, and as much as some people whose salary depends on it might say otherwise, they are not the (only) future of Nix: they are simply a special entry point for Nix code with a built in pinning system, nothing more, nothing less.

Nix continues to gather a reputation for bad documentation, in part because the official documentation for nixpkgs and NixOS is de facto not allowed to talk about flakes, as a policy. This situation is certainly partially due to a divide between Nix developers and nixpkgs developers, which are groups with surprisingly little overlap.

Flakes also are a symptom or cause of much intra-community strife between “pro-flakes” and “anti-flakes” factions, but this situation is at some level a sign of broken consensus processes and various actors trying to sidestep them, an assumption by many people that the docs are “outdated” for not using flakes, and the bizarre proliferation of flakes everywhere in blog posts or tutorials leading to a belief that they are required for everything.

This post is about how to architect Nix projects in general, with a special eye on how to do so with flakes while avoiding their limitations. It tries to dispel misconceptions that can develop in such a monoculture.

Read all of Flakes aren’t real and cannot hurt you: a guide to using Nix flakes the non-flake way

nearly every person that creates a lemmy account, is active

This is false. There’s about a 10:1 ratio of Lemmy accounts registered to lemmy accounts posting comments.

It’s an original work in the style of XKCD

The only mistake I see is attributing the work to XKCD.

🤫

I also did not create this.

This is original work. The source is in the post.

Randall Monroe has provided me with weekly nibbles of entertainment for nearly 2 decades. But this was inspired by his style, not created by him.

You want to talk about it?