Earlier quoted context omitted.
Important to note that it’s not hard or swimming against the current - you just use the nonguix channel, which has all of those things and is a perfectly acceptable use of the system (it’s what channels are for) - but it’s not in the default installation.
>you just use the nonguix channel Opened up https://gitlab.com/nonguix/nonguix . Literally the second sentence in the project information section, top of the page: "Please do NOT promote or refer to this repository on any official Guix communication channels." Weird thing to say something like this there. Too ideological for someone who wants to get stuff done.
Guix on the Framework 13 AMD
31–40 of 198 posts
Re: Guix on the Framework 13 AMD
#32My kingdom for Wayland fractional scaling that doesn’t make my apps blurry. It makes the feature a complete nonstarter for me.
See the screenshot of my settings: https://imgur.com/a/VQHD5vT
Re: Guix on the Framework 13 AMD
#33The sell is that it's very recoverable - in theory you can rebuild from a single file. That's very appealing for VMs that need to be moved about.
Unfortunately I needed a couple of things that were available only through apt. Now, Guix said it was perfectly happy to mix package management, (a bit like mixing pkg and ports in BSD) - but don't do that. It all went horribly wrong with confusion over which binaries were running at any time and when I did try to port it, it broke.
I like lispy things so will give Guix another try one day, but it needs you to fully embrace its philosophy and no half measures.
Re: Guix on the Framework 13 AMD
#34Earlier quoted context omitted.
That is not the case on wayland. Wayland applications with support for the fractional scaling protocol can render without any blur at any fractional scale. This is because the protocol negotiates the size of the underlying buffer. If the client and the compositor agree on the scale, then no scaling of the buffer will happen in the compositor because the client has attached a buffer that is the exact pixel size size o…
> E.g. it could alternate between 1 black and 1 white pixel in the physical buffer or it could sometimes make two adjacent pixels the same color. This is a very odd definition of "no blur".
Re: Guix on the Framework 13 AMD
#35"Free Software Foundation position on firmware ... is that if a device has ... firmware ... in a form that users can’t modify, then the system as a whole is not free software. This is technically correct but doesn’t logically imply that the right strategy for advancing free software is to forbid firmware blobs" It may not be the convenient thing for novice users, but it is an important strategy to "dogfood" fully-fre…
There is precedent for not taking a hard line. Nearly all GNU software works on Windows, for entirely pragmatic reasons.
Re: Guix on the Framework 13 AMD
#36Earlier quoted context omitted.
Important to note that it’s not hard or swimming against the current - you just use the nonguix channel, which has all of those things and is a perfectly acceptable use of the system (it’s what channels are for) - but it’s not in the default installation.
>you just use the nonguix channel Opened up https://gitlab.com/nonguix/nonguix . Literally the second sentence in the project information section, top of the page: "Please do NOT promote or refer to this repository on any official Guix communication channels." Weird thing to say something like this there. Too ideological for someone who wants to get stuff done.
They don't want to compromize their mission - which is to provide a fully-free operating system. But they recognize that, at the current moment, non-free software is required for many users. So they maintain an unofficial repository for non-free software, and avoid endorsing or promoting it on the official channels.
> Too ideological for someone who wants to get stuff done.
The maintainers of Nonguix are mostly the same people working on Guix, so you can expect the same amount of ideology :)
Re: Guix on the Framework 13 AMD
#37Earlier quoted context omitted.
> E.g. it could alternate between 1 black and 1 white pixel in the physical buffer or it could sometimes make two adjacent pixels the same color. This is a very odd definition of "no blur".
It works in chromium without anything I'd call blur. Here it is at 175% scale: https://i.ibb.co/DtKm69d/image.png
Re: Guix on the Framework 13 AMD
#38Had a VM GUIX "system" (really I think its more of package manager overlay) for a while (18 months ago) but encountered some problems. The main feature AFAICS is that it maintains the state of the system and packages all very cleanly via it's own nix build system which is like a snapshot of everything. The sell is that it's very recoverable - in theory you can rebuild from a single file. That's very appealing for VMs…
Nix is conceptually extremely similar to Guix, but a different implementation! It uses its own programming language, also called Nix, and has a less strict stance on free software.
Re: Guix on the Framework 13 AMD
#39Earlier quoted context omitted.
It works in chromium without anything I'd call blur. Here it is at 175% scale: https://i.ibb.co/DtKm69d/image.png
Does the scaling change the kerning of the letters? This looks horrific! (and, yes, blurry, or "antialiased" as is custom to name it).
Re: Guix on the Framework 13 AMD
#40One thing I liked about Nix was that it was possible to use its packaging and tools without actually using the NixOS. An old employer used this instead of Docker for managing build distribution. Can the Guix stuff be used the same way?