0x0

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

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.

Thank you for actually writing out what happened. I still can't make sense of Mastodon threads. Whoever had the idea to make you click "read more" on each individual post to read it needs to take a basic UX course. Absolutely unusable.

This looks cool.

What is it?

edit: About an hour later of clicking around and watching videos. Whatever it is, it's a treasure trove of interesting/innovative programs and utilities built around some kind of experimental display server. At times it's like watching Hollywood's interpretation of a future operating system. Much of it is beyond comprehension. Whoever is working on this clearly has a vision and I applaud them for it.

Every major update has broken something or fundamentally changed my workflow to such a degree that I no longer feel I understand the program. I currently use it in a semi-automated setup and I'll likely have my package manager ignore its upgrades in the future barring total breakage of the package. Note: I'm not saying the program is bad, it's just not something I'm interested in constantly tweaking/relearning if a future update is just going to break it.

I just learned about Ansel, which is a fork by someone who did a ton of work for DT but was ultimately too opinionated and got the boot. Apparently it's way more streamlined and easier to work with. YMMV.

I've also heard about vkdt, which is very early, but still something to look at.

The funniest part about all this is that so many people apparently joined the Fediverse thinking it was some rock-solid fortress of privacy when it's the exact opposite by design. I've seen multiple posts over the last week where people seem absolutely freaked out that Meta is going to be getting their data, meanwhile anyone with a basic knowledge of Docker and networking can spin up an instance, federate with everything, and get a steady stream of that data 24/7 to use however they want.

If you need privacy, use E2E encrypted chat.

Glad it worked. Have fun!

How many times is this going to get posted? We're on the fourth or fifth repost since it was written. The last post was just 12 hours ago on this community and there's still active discussion.

Been running it for a bit. Rock solid and everything is snappy.

Right? I laughed when I found out it worked, then had a moment of like, "hh, shit" when I realized the log wouldn't actually help me solve the problem at all.