Anybody try XLibre instead of Wayland yet?

[IceDigger]

Anybody try XLibre instead of Wayland yet?

Testing it out on CuerdOS and it makes the whole experience a lot snappier than Wayland on CacnyOS. Even in games.

Curious if anybody else has tried it out yet?

 

[CrimsonKnight13]

No interest since I utilize Wayland for HDR & VRR. Does XLibre provide either feature with Proton?

 

[Mazzspeed]

Wayland does everything I need and supports VRR, I've got no interest in reviving X11.

 

[atarione]

If you are interested in Xlibre I see Lunduke released an OS using Xlibre as the windowing system. Out of curiosity spun up a VM of it on my Xen Server.

 

[Fyur]

Anybody try XLibre instead of Wayland yet?

Testing it out on CuerdOS and it makes the whole experience a lot snappier than Wayland on CacnyOS. Even in games.

Curious if anybody else has tried it out yet?

I gave it a shot for a few days. My experience was similar desktop responsiveness felt a bit snappier, especially with window movement and game launches. That said, Wayland still worked better for me with a couple of apps, so I ended up switching back for now. It’ll be interesting to see how XLibre matures over the next few releases.

 

[IceDigger]

I gave it a shot for a few days. My experience was similar desktop responsiveness felt a bit snappier, especially with window movement and game launches. That said, Wayland still worked better for me with a couple of apps, so I ended up switching back for now. It’ll be interesting to see how XLibre matures over the next few releases.

Curious the wayland apps that didn't work with it? It's usually the other way around with X11 apps not working well with Wayland.

 

[Axman]

Curious the wayland apps that didn't work with it? It's usually the other way around with X11 apps not working well with Wayland.

For me it was the advanced power settings for using my laptop plugged in but capped at 60 percent charged.

As far as distros go, the Lunduke one is so new, so untested that even he considers it to be an alpha bordering on beta (since it uses "off the shelf" components). There are guides to getting XLibre running on Cachy and it's a default option on I want to say Artix, as far as for more mature builds go.

XLibre was stifled so long by its handlers that it's still got a ways to go, I think, before it becomes a mainstream option again, but on the flipside, development is happening so fast and with so much support that I don't expect it to take all that long, either.

 

[IceDigger]

For me it was the advanced power settings for using my laptop plugged in but capped at 60 percent charged.

As far as distros go, the Lunduke one is so new, so untested that even he considers it to be an alpha bordering on beta (since it uses "off the shelf" components). There are guides to getting XLibre running on Cachy and it's a default option on I want to say Artix, as far as for more mature builds go.

XLibre was stifled so long by its handlers that it's still got a ways to go, I think, before it becomes a mainstream option again, but on the flipside, development is happening so fast and with so much support that I don't expect it to take all that long, either.

Now you just need to find the version written all in assembly

 

[atarione]

For me it was the advanced power settings for using my laptop plugged in but capped at 60 percent charged.

As far as distros go, the Lunduke one is so new, so untested that even he considers it to be an alpha bordering on beta (since it uses "off the shelf" components). There are guides to getting XLibre running on Cachy and it's a default option on I want to say Artix, as far as for more mature builds go.

XLibre was stifled so long by its handlers that it's still got a ways to go, I think, before it becomes a mainstream option again, but on the flipside, development is happening so fast and with so much support that I don't expect it to take all that long, either.

Isn't Lunduke OS just Deuvan in a hat though?

 

[uOpt]

Wayland can go where the pepper grows.

 

[cjcox]

While Wayland (even with XWayland) is still pretty far from handling what Xorg did, and it may still be years, and in some cases never because the Wayland world has taken a much more "Windows-esque" view of the desktop as not being an "application" but being "the client" (emphasis on the word "the")... even so, that Linux needs to have the same limitations as Windows mindset means that all focus is on "the (single user) client" desktop UI. So, like it, hate it, it's "what is" and where everything is being forced to go. With that said, there's a lot of "stuff" in X11 protocol that doesn't make sense to most anymore, but maybe it should (?)

Anyhow, IMHO, Wayland/XWayland and today's requisite compositors have more in common with being "Windows" (in some of its worst ways) than having a "unix like" mindset. For some, because they are Windows users, they want that. For people living la vida "anything" (the Unix way), not so much. Old gray beards will talk of single servers handling many full desktop users.... and the youngsters will yawn (that is, saying, "we don't care about that").

Sadly, this has a trickle down affect. That is, features like SR-IOV and flexible GPUs across virtualized environments also gets impacted by the "why do that?" crowd. Not liking the effect one bit.

Shorter term fall out, older native X11 games (native ports) will soon cease to operate in our "new (better?) world" because of the removal of all 32bit support across the board. Sigh. But, we can also argue that's the problem with not developing FOSS but using closed source. Oddly, Windows 32bit software (even closed) will work longer term on Linux than native 32bit (due to wine), which is just a strange thing to say out loud.

Wayland/XWayland pluse requisite (and plethora of different) compositor doesn't have to suck, but making it "not suck" isn't on the priority list. With that said, it will (maybe?) get there someday. I say that because it's very likely we'll have Wayland's replacement on the table (and it will be reinvention... again... sigh) before Wayland/Xwayland+requistie compositor gets to where (IMHO) it needs to be.

 

[CrimsonKnight13]

While Wayland (even with XWayland) is still pretty far from handling what Xorg did, and it may still be years, and in some cases never because the Wayland world has taken a much more "Windows-esque" view of the desktop as not being an "application" but being "the client" (emphasis on the word "the")... even so, that Linux needs to have the same limitations as Windows mindset means that all focus is on "the (single user) client" desktop UI. So, like it, hate it, it's "what is" and where everything is being forced to go. With that said, there's a lot of "stuff" in X11 protocol that doesn't make sense to most anymore, but maybe it should (?)

Anyhow, IMHO, Wayland/XWayland and today's requisite compositors have more in common with being "Windows" (in some of its worst ways) than having a "unix like" mindset. For some, because they are Windows users, they want that. For people living la vida "anything" (the Unix way), not so much. Old gray beards will talk of single servers handling many full desktop users.... and the youngsters will yawn (that is, saying, "we don't care about that").

Sadly, this has a trickle down affect. That is, features like SR-IOV and flexible GPUs across virtualized environments also gets impacted by the "why do that?" crowd. Not liking the effect one bit.

Shorter term fall out, older native X11 games (native ports) will soon cease to operate in our "new (better?) world" because of the removal of all 32bit support across the board. Sigh. But, we can also argue that's the problem with not developing FOSS but using closed source. Oddly, Windows 32bit software (even closed) will work longer term on Linux than native 32bit (due to wine), which is just a strange thing to say out loud.

Wayland/XWayland pluse requisite (and plethora of different) compositor doesn't have to suck, but making it "not suck" isn't on the priority list. With that said, it will (maybe?) get there someday. I say that because it's very likely we'll have Wayland's replacement on the table (and it will be reinvention... again... sigh) before Wayland/Xwayland+requistie compositor gets to where (IMHO) it needs to be.

Keeping multilib or lib32 works well on Arch. Not sure how other distros are maintaining or nuking 32-bit software on their repos though.

 

[cjcox]

Keeping multilib or lib32 works well on Arch. Not sure how other distros are maintaining or nuking 32-bit software on their repos though.

It's just like Xorg.... I suppose you could keep on using it (?) But doesn't sound wise in the long term.