I’d just like to interject for a moment…
They have a list on their project page. I pretty much only use the clock and date features right now. It’s kind of a shame that the main swaylock project isn’t interested in adding a clock. Swaylock-effects also seems to be able to blur images, but i chose to do it with imagemagick instead.
Well i guess rice is a bit of an overstatement, since swaylock/swaylock-effects doesn’t have a ton of options besides some coloring mostly, but this is what my config looks like. Some of it like the clock stuff is specific to swaylock-effects. I used a few basic colors from gruvbox, and i use a script that swaps out the colors to different themes that i use. Other than that i just put a blurred version of my wallpaper as the background image that i blurred with imagemagick.
Another vote for gtklock. I liked it and used it for quite some time. I switched to swaylock-effects a while back purely because i switched to a distro that didn’t have gtklock packaged, and i couldn’t be bothered to package it myself. After i actually put some effort into ricing it a bit i’m not hating how it looks so i think i’m sticking with it. I suppose you could also try hyprlock since it has a password field as well, but i keep seeing tons of posts that show it crashing, so idk how reliable it is. From what i’ve seen it can be made to look really good though.
I’m assuming he means that it’s harder to tell? But swaylock will still inform you when it’s cleared out so idk.
Yeah, with all the stories i keep hearing about it, next time i’m in the market for a GPU, i’m not buying anything that has this connector if i can help it.
At first i thought you meant just choosing an init with the installation ISO like Artix. but according to the article you can choose an init at boot, that’s pretty cool.
As a linux user on amd i’m just happy to hopefully finally get hdmi 2.1 support lol. I’ll probably be good for a long time after that considering 4k 144hz is already hard to drive.
It’s possible, but at the very least someone glances over the derivation since it’s part of the actual nixpkgs repo right? AUR on the other hand is a wild west.
Looking at the average pc gamer’s desktop, sounds like a 1000 IQ move to me.
Hmm, i should probably experiment with it in a vm at some point, but from what you’re saying it sounds like it works ootb. In that case i would say Guix definitely handles this better. Nix packages that need graphics drivers don’t work ootb, because it expects the drivers to be in /run, because that’s where the drivers are on NixOS, and they can’t use the host drivers. NixGL tries to solve this, but i stopped using it because it causes other problems. For example, if you install a wayland compositor through nix and run it with the NixGL wrapper, if you then try to run a game or something that needs the host drivers, it won’t work because everything launched inside of the compositor inherits the NixGL status. So now i manually create a driver package and symlink it to /run, that way there is no wrapping and the drivers don’t conflict with each other, but it still feels hacky. I can also imagine it’s very inconvenient for someone who’s just getting into Nix and just wants to install a few things in a profile to be running into that issue.
I’ve found that depending on what distro/OS it is certain methods of burning the ISO don’t work correctly, no clue why. Windows needs their official tool, so because of that i use a vm to burn it. I’ve also had linux distros that couldn’t boot when dropping it onto a ventoy drive, and would only work when directly burning it with dd, so it might have something to do with what ISO you’re trying to burn and how you’re burning it.
I’m using Guix system so it’s not really relevant to me right now, but since you mentioned you’ve used it on foreign distros, how does Guix handle programs that need graphics drivers? When using Nix on foreign distros, the graphics drivers are handled in a weird way where you either have to use a wrapper like NixGL, or, what i do right now, is create the driver packages manually and symlink them to /run, which is how NixOS does it. Do you need to do anything special on the Guix side of things? I noticed that Guix system does not have its drivers in /run, so they must be doing it differently.
Idk, you’ll have to ask the xlibre dev lol
I’m assuming those 5 other games are too heavy to be considered “running” on it? Cause if we’re talking purely about software being able to run on the OS then i don’t understand how windows games would not be playable on windows.
Mainly their readme being fully magat-pilled, talking about DEI and whatnot. They also waste time on things like renaming functions to own the libs. It’s not a project that i put any trust into and i’d rather use plain X11 if i had to go back.
Multi-monitor issues surprises me, considering multi-monitor support is kind of a sellingpoint for wayland. I don’t think animations being incorrect has anything to do with wayland itself though, it’s up to the individual compositors to handle that.
Same goes for buying a console. It’s expensive across the board