.NET is such a second class citizen (Mono situation looks shaky now) on non-Microsoft Windows. I mean don’t give it up cold turkey perhaps, but adding new languages to your belt will help you get unshackled from Microsoft.

Git is distributed but still centralized. D in DVCS is distributed. Downvoters likely have never used a non-Git VCS, let alone a non-snapshot-based VCS. But fanboys will fanboy.

Pijul & Darcs are based on Patch Theory which make the conflicts of different patch order a non-issue so long as the apply cleanly (such as working on different ports of the code base). Patch A then patch B ≡ patch B then patch A; this will be a needless merge conflict in Git since the order matters. (& no, Jujutsu isn’t the solution still shackled to the limitations of Git as a back-end while claiming to do what Pijul does—but doesn’t).

Darcs & Pijul are based on Patch Theory. https://darcs.net/Theory

Git being snapshot-based unlike other (better) VCSs require that patch order matter so often the easiest way to manage a project is to have some centralized authority since it is so, so easy to get merge conflicts without a central authority if trying to just distribute patches. It’s a lot easier to be decentralized without Git’s fundamental limitations.

Anyway it is a good habit to avoid github entirely (when hosting a repo).

FIFY

A “hub” implies centralization, no?

Happy I switched to NixOS to solve this issue for myself

That is a different story & a usability pain I can share 😅 …but assuming there wasn’t a GC, the build is cached, just needs another switch—& I am willing to take that as opposed to having the whole process running as root.

It’ll call sudo at the point it needs to at the end regardless of remote or not. There have been a couple of bugs in the past trying to run the whole process under sudo & --use-remote-sudo was always recommended as a fix.

You should at least consider nixos-rebuild --use-remote-sudo switch over raw-dogging sudo.

#!/usr/bin/env dash

set -e

cd $HOME/nixcfg

# flake inputs to update
for input in nixpkgs nixos-hardware home-manager hosts; do
	nix --extra-experimental-features flakes --no-warn-dirty flake update $input
done

# rebuild NixOS
nixos-rebuild --use-remote-sudo switch --keep-going --fallback --flake $HOME/nixcfg#$(hostname)

# check for firmware upgrades
fwupdmgr get-updates

# print hard drive status info
sudo smartctl -H /dev/nvme0n1
sudo zpool status -v -x

Just please get us proper color management. Creators need accuracy & HDR is still a mess.

To say it was written in Rust & make it someone’s portfolio piece so they can use a Microsoft GitHub link on their Microsoft LinkedIn profile.

They don’t package LTS kernels which is pretty concerning—especially if using out-of-kernel modules that don’t always get released in lock step that could leave you with a machine that won’t boot.

To be fair, there are NC software licenses out there under umbrellas like post-open source, copyfair, & copyfarleft. Creative Commons is wrong for this application—& ND is even more questionable—but choosing to follow these other movements is something you can choose to do or support if the noncommercial clause aligns with your philosophy (but incompatibles with GPL & friends can prove difficult).

Great to know. I saw it missing from the support table & just assumed that was that.

“FOSS” here doesn’t mean hosted exclusively on proprietary Microsoft GitHub, right?

Naïve me it college hearing non-destructive editing was right around the corner. The corner was well over a decade. 😅

Yep. Camera situation is shit. I often carry a mirrorless so I can get a nice photo if I need it, but it means a general photo by me is shit since you need that proprietary software. And yet still since I use the headphone jack more than anything, it is a requirement—along with an unGoogled experience for privacy. If you want a jack + unlockable bootloader with flagship specs, Xperia is the only line left.

That is a real concern & it seems they are moving to 4 years of updates as well as not rolling out a new phone every year, but given that LineageOS supports the phones, even if I am not getting firmeware updates, I am willing to take that risk since I get more IO.

The Xperia 5 is a skinny 6.1" & many consider it to be a small phone option in 2024.