On that front: to developers-

Please make sure you include bash completions for your tools

pre installing flatpaks

Did the room just get a bit colder or is it just me

Libreoffice has a database engine and frontend that’s pretty applicable to Microsoft Access

guix and/or nix

Both are functional package managers and manage dependency trees better than flatpak IMO (also the package description languages mean you can manipulate the package definitions at install time much easier)

If you can’t find a package in guix/nix then it behooves you to use flatpak

Biggest problem to open source health adoption has been the extreme unwillingness to form an international standards group around diagnoses and labeling.

Closest we have is the WHO with ICD but for some fucking inane reason it’s only used reliably by the second and third world. (Ironically this means most African countries have freakishly good digital MAR interop when they can afford to put in a system that uses those standards.)

Some additional nice things about guix:

Everything is guile. The system definition, the service definitions for shepherd, everything.

Shepherd is hands down the best init program I’ve ever used. It’s just incredibly simplistic but because it just runs the guile definition you give it, you can do some incredibly complex things that systemd etc. can do as well.

The OS documentation is built into the distro, with “info guix” you get reams of configuration information for the distro without ever needing to look it up online.

About a year and a half.

To be honest it’s not “easy” to use. The guiding principle behind mainline packages is that everything has to be built from source, so most somewhat unpopular things are missing from the mainline channels.

To use it like any other distro you’re going to need to learn how to write packages fairly quickly. Luckily the main draw of guix is the entire OS being based on guile so once you get a little under your belt you can just read the specs from other channels to see how a package is written.

Took me maybe a week to start writing guix packages.

There’s also The toybox

Guix because I love the idea behind Nix but Nixlang is the most painful language I’ve ever had to type out.

Hledger!

Command line, plain text files so anything can read them, and GPL!

I’d say this seems useful mostly for pulling non nbz/torrent sources from readarr and lidarr services

I highly recommend Obtainium to anyone who wants to keep their apps updated without needing a central report (save for the APKs that only publish on f-droid etc)

It was over eleven years ago at this point so my memory may be hazy on the details but I remember something happening in the major version change that pissed me off enough to switch off of it. 🤔

Licenses for sublime text 2 just said “and future updates”. I remember the “lifetime” thing being a selling point on producthunt. This was back in 2013 though, and the weird way the licensing change was handled made me switch to emacs.

Before sublime text 3 all updates were included in the single license, not just major revision updates. This was back in 2013.

Before the one license=one version switch in 2013 the license stated “and future updates” which they did, but they switched to needing to pay for new licenses for some reason. I remember that being the primary reason I switched to emacs.

After having been shafted by sublime text I will never believe anything called a “lifetime subscription” is such.

A “lifetime subscription” is just a “until we decide otherwise” subscription

The leadership response to this and the subsequent backlash is starting to remind me of the NixOS debacle from about a year ago.

That resulted in the project being split and like 30% of the community moving off and creating Lix.

I would be disappointed, but not surprised, if we see something similar in the Kernel sometime in the next year or two…

Man you better hope the kernel community gets its shit together then, cause Krummrich (the primary developer for nova and getting those changes upstreamed) is one of guys that got told their project was cancer by the “thin blue line” maintainer (Hellwig) from the article.

Nouveau is important because Nouveau is the default driver in Ubuntu, Fedora, OpenSUSE, Debian, and ever other distro.

Linux distributions can’t easily distribute the proprietary nvidia drivers or the slightly less proprietary nvidia-open drivers so they depend on nouveau as the default nvidia driver. When you install a distro it usually has to use the nouveau drivers before downloading the proprietary blobs from Nvidia.

Nouveau is the only reason anyone can use Linux on an Nvidia card long enough to install the other drivers.

It’s also actively maintained, receiving updates that get upstreamed almost daily.

I’m not sure what about those things says “defunct”.

And the rust developments in Asahi for the M1+ series of CPUs don’t just benefit Mac but all the ARM CPUs as well.

A few people from a downstream project like Asahi or an almost defunct driver like Nouveau

I’m not sure why you think Asahi is a minor player in the linux community when they’re responsible in the entirety for porting Linux to the Arm-based Mac M1+ series, or why you think Nouveau is defunct.