Guix users looking around shiftily and sweating

> restricted

More like walking into fansub channels and doing !get and walking away with DC++ info

For awhile Firefox’s JavaScript engine used more memory, but those gaps have been mostly filled.

Easiest? Tailscale., set it up on the server and each client you want to access it and it creates auto-resolving P2P VPN tunnels between them all.

I2FS?

DirectML sucks but ROCm is great, but you need to check if the software you want to use works with ROCM. Also note there’s only like 4 cards that work with ROCm as well.

ROCm is comparable but very few applications work out of the box with it.

The fun part is that you don’t have to do all that stuff if you have a long term visa.

Good luck! Feel free to DM me I’d you have any questions!

You can start a different TTY than the install automatically starts. Guix has a ‘guix system init‘ command you can point to a system config and mounted filesystem, much like arch’s system init.

If you use the curses-based installer it auto-generates a system config file for you.

Note that the base configuration is entirely libre kernel so some drivers may not work (like wifi)

In order to get these working out of the box you have to make a boot iso with guix with a non-libre kernel.

The system crafters channel has a guide that details using nonguix (a non-libre kernel channel) in the installation out of the box: https://systemcrafters.net/craft-your-system-with-guix/full-system-install/

Doing a reconfigure right after a pull and half the packages don’t have substitutes yet 😭

Active GuixSD user.

Our application catalog is much smaller than many other distros simply because we don’t have the userbase large enough to surface the volunteers necessary to support it. So you will have to learn to write your own packages eventually

That said, if you know your way around functional languages (in this case, scheme), it’s probably the easiest time I’ve ever had writing a package. Everything that goes into the script is known at the time the script is written, so weird extrinsic problems don’t really occur after you’ve written the package.

Some stuff that you and the guix maintainers may not have the time to support will also get updated more slowly.

Luckily flatpak exists, and is a godsend for the new wave of read-only (functional/ostree-based) OSs.

Biggest appeal for me was having all my configuration in one place (and documented) so if I forget I did something in 6 months, it’s always staring at me in my home or system config file. You can accomplish the same thing by being diligent with say, script files, but it’s drop-dead easy to just maintain a system and home descriptor file and keep editing that.

I’ve been using the beta. The HDMI CEC features are very nice but the operation is still spotty.

Yea like moving all the food on the top shelf of your fridge to the bottom and moving everything up shelf by shelf every morning or making sure you vacuum your walls properly. Standard stuff.

It seems like a very polarizing game, you either really enjoy it or not at all.

I love the division 1 and 2 but the first game had some MAJOR bullet soak issues for the first half-year of the game’s lifetime.

Massive always does good work despite Ubisoft, in my opinion.

Do image previews work over SSH? I admit I’ve never actually tried it…

I wouldn’t bother unless you find yourself doing more through the terminal than through GUIs.

I don’t have a built-in file browser (not using a DE, just i3 window manager), so I use ranger and pure GNU coreutils commands mostly but I still find myself missing the drag-and-drop features that FreeDesktop integration provides for stuff like nautilus.

The problem is that the Linux kernel is monolithic so introducing rust into it does have certain repercussions about downstream compatibility between modules.

Right now the rust code in the kernel uses c bindings for some things and there’s a not-insignificant portion of C developers who both refuse to use rust and refuse to take responsibility if the code they write breaks something in the rust bindings.

If it was pure C there would be no excuse as the standard for Linux development is that you don’t break downstream, but the current zeitgeist is that Rust being a different language means that the current C developers have no responsibility if their code refactoring now breaks the rust code.

It’s a frankly ridiculous stance to take, considering the long history of Linux being very strict on not breaking downstream code.

> Kinito Pet now playable

How the fuck is that gonna work