Is there a reason those features weren't added to data classes?
I don't know much about attrs, only professionally coming to python since 3.7, but I'm not going to bring it in if there's something sufficient in the language
Not really, other than they decided to keep data classes very minimal, as standard library comes with maintenance costs (you can't get rid of a feature once you add it), so they kept the strict features, since everyone uses those, and not the complex validation features.
> It would be quite comical if the 300lb figure were correct, having lugged one around before. They hovered around 92lbs, though.
I might be mistaken then. There was also a Trinitron in the room, 30-something inches and required 3 people to pick up. The FW900 certainly felt like 300lbs, for a single person.
I have one of the variants(HP A7217A) sitting away gathering dust at a relative's place. Its weight/size just made it too difficult to move with over the years.
I hadn't realized they're still desired now. I'll have to dust it off and see if there's a buyer out there.
Just install the standalone Nix installer like you would on any other (non-Nix) distro (see this part of the Nix manual: https://nixos.org/nix/manual/#chap-quick-start ). Both Guix and Nix are designed to work on top of 'foreign' distros, and this includes using a standalone Nix package manager on GuixSD and a standalone Guix package manager on NixOS (or both the standalone Guix package manager and the standalone Nix package manager on top of Arch Linux, etc. etc.)
This[1] is the one I used as a reference for my kernel build which includes brcmfmac
There is also a feature called 'channels' (not widely documented AFAIK) which allows you to describe an outside repository of code you can reference to install packages. There is one[2] that provides Chromium (though I cannot get the build to succeed).
The downside to all of these not being provided in mainline is the amount of time and energy to build them. I suspect there are more people than I would like curating their build of the linux kernel, manually specifying drivers included in the kernel. I really wish the community were a little less hard-set on the principle of 'freedom' and a little more pragmatic; I am sure the community is smaller due to people being turned away at the sheer amount of effort required to get their machine to a usable state.
As someone who is sympathetic to their cause and their stance, I think the extreme position of excluding all non-free software can actually hamper the movement by making it less accessible to people. I get you always have to draw a line somewhere, but FSF draw it too firmly.
> you always have to draw a line somewhere, but FSF draw it too firmly.
They actually don't draw it exactly where I would. I don't care so much for games if they're open/free or not (it's nice when they are of course), but I am concerned with unauditable code on, for instance, the SATA controllers in my machine, even if it 'read only' code. Where the FSF is more concerned with the first and less with the second.
On the other topic, I think the ability to create (and share) your own recipes/channels for software on Guix allows for people to create fairly easy ways to install non-free software (or using Nix on top of GuixSD) without the Guix team having to support unethical software.
I haven't kept up with the goings-on in this release, but I was quite excited to see so many clamoring for resolutions to pains involving multi-monitor setups in a previous discussion[1]. I would be interested to see what of those pains have been fixed.
Great quote. I hadn't known before it was Keynes