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).

“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. 😅

The advantage here is that you can start baking in animations, themes, progressive enhancements. I would agree this isn’t the best tool for most authoring, but considering tow lackluster the XML editor is in Inkscape & how break points can make sure your icon is clear at all sizes, it is a good idea to spend time in a text editor as well.

Starhacking is a thing. When you see words like “blazing fast” & emoji all over the README it show the maker is treating the code as marketing—& MS GitHub is a social media platform with algorithms.

There are several browsers that can operate with low memory requirements, but you have to be willing to live without JavScript & the front-end needs to have been built with accessibility & progressive enhancement in mind. …Which most front-end developers don’t do & the industry doesn’t normally pay them enough to care or get better results (& following YouTube tutorials always tells you to use the latest bloated framework which is overkill for your project).

Also Fedora doesn’t ship with LTS kernels which makes me question their package management strategy.

Which is largely whether or not the eventual consistency model or not is the route to take. Is the resilience for chat worth the explosion of storage & preformance cost of sync/search & maintaining all that data amongst all servers? Or is limited/functional sync without always duplicating the entire history with the occasional out-of-order message & missing old attachments good enough? Is ephemeral chat okay to save resources which in turn makes it more feasible to self-host on lower-end hardware or is it better to trust a couple big servers with massive storage who probably have admins?

This is how they want to frame it. C has footguns, therefore use Rust—instead of Rust is one of the options you could use.

Correct me if I am wrong, but my understanding is that you use Coq to prove your theroem, then need to rewrite it in something else. I think there is some OCaml integration, but OCaml—while having create performance for a high level language & fairly predictable output—isn’t well-suited for very low-level kernel code. The difference in the ATS case (with the ML syntax similarity 🤘) is you can a) write it all in a single language & b) you can interweave proof, type, & value-level code thru the language instead of separating them; which means your functions need to make the proof-level asserts inside their bodies to satisfy the compiler if written with these requirements, or the type level asserting the linear type usage with value-level requirements to if allocating memory, must deallocate memory as well as compeletly prevent double free & use after free.

For those in the back: Rust can’t do this with its affine types only preventing using a resource multiple times (at most once), where linear types say you must use once & can only use once.

deleted by creator

Yet even without a WM, still better than macOS

If you believe in ADTs, limiting mutation, & a type system that goes beyond Rust’s affine types + lack of refinements (including a interleaved proof system), you could be writing kernel code in ATS which compiles to C.