0x0

How's the grind?

Does a scheduler impact power draw? Maybe you're confusing this for a CPU governor perhaps?

And yes, the underlying tech here is user-configurable schedulers. Very neat.

For those getting excited, It doesn't "boost" gaming performance. It prioritizes the game over the background process (in this case, a kernel being compiled.)

Schedulers aren't magic. As pointed out in the comments of the linked article, there are other ways of doing this. The more interesting tech here is being able to choose between schedulers under specific workloads, which is very nice IMO.

I recommend an RX 580. Older card, but better than the 1060 and 8GB instead of 6GB. Good for 1080p gaming at 60fps and can be workable up to 1440 if you lower settings. Used price is around $60 - $90 USD (down from $110 when I bought it earlier this year used on eBay.) Only thing to look out for is the bios switch, which downclocks memory if in the wrong position. I drive 3 displays with it and used to do 4 with no issue on Wayland. Highly recommended for a budget card.

I get Bad Company 2 vibes from this. Might give it a shot.

New GITS?

I'm with you 100%. Hopefully more admin overreach will push users off the offending instance in question and remove it from relevancy.

Anyone watched it? I kinda skipped through the last few episodes but wanted to give it a shot again.

Switched from BORE to EEVDF (which is now the stock scheduler after 6.6 IIRC.) EEVDF works better under load.

Mpd has always served me well. I use ncccmmmmppp (however its spelled) to manage playlists and such. For album artwork I run sxiv pointed at file in /tmp/. I forget how that part works, actually. I have a grid layout on a second monitor, so I just square up the mpd client and sxiv. Doesn't look too bad.

Semi-related, but as a project I ripped out the pressure/impact pads of an old midi keyboard for use as prev/(pause/unpause)/next buttons, so if the song sucks I can literally punch my desk to skip it.

Wayland has mostly positive user reviews because it presents nicely to the user (VRR, scaling, etc.) On the developer front it seems there's a lot of struggle over things that were solved in X11 but for some reason require a lot of debate in Wayland.

• There's still no way to universally configure monitors and input devices, so the startup cost to checking out a new "WM" (compositor in Wayland terms) is non-zero - you have to reconfigure everything from the ground up, and for anyone with complex input systems (see: accessibility devices) this will take a lot of time because each compositor insists on using a different format for configuring these things.
• Each compositor is tasked with coming up with solutions for all parts of the user experience (hence the last point) and thus anyone who wants to experiment with making their own WM now has to worry about a billion things that wouldn't have had to deal with in X11. Yeah, there's libraries for dealing with that stuff, but it's not as simple as it was and lot of innovative WMs won't ever be able to make the jump.

These are the two biggest issues I can see that are entirely chalked up to its design. Technical issues (like the "load balancer" thing that keeps Firefox from crashing on Wayland) will be solved in time. However, the above points are unlikely to ever be addressed. Should they be? I don't know.

I'm fairly certain they're a college student also.