In theory it makes sense to replace X with something cleaner, but wayland came out of the same cesspit as systemd so I very much worry.

>>109120045
of what?

>>109119992
based zased baste basado blazed
taskbar when

>>109119992
for a light and quick DM xfce or lxde?

>>109120119
xfce isn't as light as it used to be

Ok but when will it be ready for stable use

>>109120137
this mint cinnamon install isn't that great, the file manager doesn't support viewing thumbnails when trying to upload a pic on this blasted site so you have to tediously scrutinize the filenames

>>109119992
Not looking forward to Fedora shoving this into the Xfce ISO before it's actually usable.

>>109119992
Another Wayland W.
Will they change the name to WFCE?

>>109120119
lxde is deprecated for lxqt iirc, the latter is decent if the you want the most minimalist DE.
>>109120137
What's the difference between old versions and the current one?
>>109120181
>Will they change the name to WFCE?
No, somewhere (probably orange site) the dev said they would not. It will be just like how XDG used to stand for X Desktop Group, now it's general.

File: 1752822602001831.jpg (44 KB, 525x525)

44 KB JPG

>>109119992
>makes a separate wm/compositor for wayland instead of shitting xfwm
Based, xfce4 chads preserving the final user agency. Gnome and KDE cucks couldn't even.

>>109120181
The X stands for X-forms, not X11

xfce4 chads are making their first baby duck steps

File: 1748053487371544.webm (3.92 MB, 404x720)

3.92 MB WEBM

>>109119992
Good day for rat-chads.

>>109120411
ratgirl is the best sex, but oh my god her apartment will be more filthy than a bombay sewer

>>109119992
honestly it feels pretty alright, pretty smooth. for what's basically an alpha I thought it'd be in a much worse state. still kind of shits itself under high load like early wlroots though

>>109119992
Does it do touchpad gestures for window/workspace management?

>>109119992
could not get wallpapers to work anybody else

>>109119992
>2026
>wayland alpha
the absolute state of xfchuds

>>109123589
Xfce exists for taking things easy, features get implemented slowly but steadily without breaking (or removing) stuff. If you want upstream, cutting edge shit immediately move to another environment.

>>109123608
We hit Wayland 1.0 in 2012. Fedora and Debian went Wayland by default in 2016 and 2019, respectively. I like slow and steady, but this is ridiculous.

>>109123715
Nah, it's exactly how it should be. Let updooters deal with bugs and shit for years, xfce chads just reap their fruits once matured without efforts.

>>109123741
Except I'm actually forced to deal with bugs if I run Xfce as the Intel driver for my graphics card does not support tear free on X11. Your assumptions are unfortunately outdated.

>>109123748
Just enable the compositor.

>>109123761
And this stops tearing with X11 modesetting on Intel graphics? It didn't for Cinnamon.

>>109119992
That's cool and all, but what about thumbnails and side bar image previews for file picker windows?

>>109123771
I don't know what to tell you, i used xfce4 on intel graphics in the past (with compositor enabled) and never noticed tearing, but maybe it's something circumstantial that escaped my experience.

>>109123781
Maybe you don't require fractional scaling, without which my system is basically unusable

File: 1751055340242718.png (586 KB, 829x800)

586 KB PNG

>>109119992
But how is the latency compared to uncomposited XFCE? How long until xfce forces me to use Wayland, which tends to force vsync in most compositors? Can I enable global tearing for all windows with xfwl?

>>109123054
The problem isn't that wayland or systemd don't work, it's that they are being worked on by (((red hat))) affiliated people. I'm not trusting any software that originated from corposhit.

>>109123793
>how long until xfce forces me to use Wayland
Never, because they made a separate wm for wayland (xfwl4), you can keep using xfwm with x11.

>>109123054
>only my usecase exists
Perhaps gnome may be more of your speed

File: 1772096779992008.jpg (122 KB, 540x576)

122 KB JPG

>>109123054
>wayland works fine
No. It doesn't. Wayland forces system wide double buffering. Every Wayland user is using their entire computer with an extra frame of lag. The entire protocol is completely flawed, and while Linux used to feel very snappy and responsive when compared to other operating systems, it is now forcing latency onto users in the name of preventing screen tearing.

Linux absolutely needs to present applications with a great urgency, or at the very least have an option to do so. Every application should be able to immediately reflect exactly what is on screen. Wayland, being coded by insane freaks, does not allow this, and will always have a frame of lag, sometimes even two.

Using Wayland feels like using my computer through vaseline, and you probably can't notice that because you are functionally retarded and only use your computer to watch hentai.

But hey, at least my computer is really pretty now!

https://arewescreentearingyet.com/

Even when it has been implemented, its only in fullscreen apps! Linux developers see no use for enabling immediate presentation for anything except video games! Nobody deserves latency unless they are playing epic video games! Linux is a lost cause.

>>109123905
You know what used to feel really snappy? Windows, back when it used GDI for rendering. Then Longhorn happened and DWM replaced GDI. Except in the classic Linux fashion, in attempting to be like Windows, Linux fanatics try to be *better* than Windows, over-engineering their counterpart solution and making it worse under every metric compared to the Windows counterpart.

If Wayland aped how DWM works 1:1 it wouldn't be the pile of shit that it is today, but since it's a desktop Linux project it was destined to become an overengineered shitheap, as Linux HAS to be better than Windows, whatever that means.

>>109123801
your kernel is, retard.

>>109120119
enlightenment

>>109123905
this hasn't been an issue for about a year already, even the biggest offender which was wlroots already fixed that
your hardware is failing, get a job and replace it

>>109123748
for what it's worth, xlibre comes with tearfree enabled by default. it's the only way I ever got tearfree to work on intel

>>109123771
Cinnamon doesn't support tearing/disabling compositing unless it's for fullscreen windows. it shouldn't be tearing in the first place since it's always compositing in the desktop

>>109124124
if we didn't overengineer our counterpart we'd be running a shitty bloated vibecode OS that takes half a century to display a menu like windows does even on high end hardware. you have no idea how just superior modern linux FS solutions are to NTFS/ReFS on shitdowns. if windows switched to BTRFS/XFS/F2FS it'd be so much faster now

>>109125090
Wayland is worse than DWM. Plus, no one uses your meme filesystems, at least no one that isn't an Arch tinker tranny. It's either ol' reliable ext4 for workstations or ZFS for servers.

>>109125057
>xlibre
How is it today, metux didn't kill ximself already?

>>109125108
>arch tinker tranny
quite the contrary, my time is valuable so i use proven solutions. the filesystems i'm mentioning have decades of enterprise support and are deployed everywhere. distros other than arch have failed to provide these solutions in a hassle free way. windows also can't give me that and f2fs is much faster than ext4 or ntfs on NVMe ssds, which is decade old tech so quit being a baby duck. also i see no issue with wayland other than the double buffering, which can be solved by a protocol extension. not having a giant server full of legacy cruft, a networking model meant for the 80s and a wide open scope is a win for linux people.

>>109125114
>metux didn't kill ximself already
he's the opposite of a tranny, anon. he will make pussies and trannies cry for many years to come.
>>109123748
>the Intel driver for my graphics card does not support tear free on X11
just set up picom then

>>109125000
Fuck off. I work with Linux professionally and have much better computers than you. You have absolutely nothing to against my words because it is objectively true that Wayland has more input lag than uncomposited xorg, by design. Suck my cock.

File: SKnIKv.png (53 KB, 1568x186)

53 KB PNG

>>109125778
Suggesting that everyone who wants to develop xlibre should be seen equally regardless of personal views or politics was so gross and discriminatory that he had to remove it. How could he suggest such an offensive thing

>>109127590
It pissed off trannies so he removed it. There is still no code of conduct, so no real change.

File: Screenshot_20260624_162748.png (7 KB, 426x57)

7 KB PNG

>>109123905
womm, get a better desktop

>>109127693
not him
>Every application should be able to immediately reflect exactly what is on screen
>Even when it has been implemented, its only in fullscreen apps!

>>109127714
so turn on VRR, idk what to tell you anon or "adaptive sync". This is not an issue on KDE Plasma, get a better desktop.

>xfeces
libawaita GTK4+ xboxhueg titlebars when

>>109127738
their whole issue is they run on dogshit hardware from 15 years ago, ancient thinkpads with like 2gb of ram and expect support forever. Which they can do with like Mate or Gnome Flashback or Katana Desktop, but they endlessly bitch about progress because it is driving up user market share. They don't want people joining their little club so they are shitting themselves. I wish I were trolling. They don't want (you) using Linux.

>>109127667
Yeah I know, I'm just so put off that we live in an era where you can say everyone is equal and people will be mad because equality is discrimination to them and you should instead be promoting special treatment for specific groups

>>109127667
It just reminds me of how every project that is not explicitly right wing will become left wing. In a year or two when the project has been proven and they can't just wave it away anymore, they'll make a coordinated effort to either get the creator to disavow far right contributors, make some type of leftist political statement, or they'll try and oust him from his own project. Him removing the old message in an attempt to 'clean up' the project is the first sign, and removing anything that gatekeeps these censorial retards is what allows them to propagate. If they have a forum or discord then it'll likely be the place that starts having strict 'no transphobia rules' first.

did any one of you that tried the preview release of xfwl get wallpapers to work?
can't tell if feature's missing or it's borked for me

>>109123715
Wayland 1.0 is like DOS 1.0. Nobody would consider DOS 1.0 to be a feature complete system.

>>109127693
>in fullscreen windows
Congratulations! You proved my point! The protocol only works for fullscreen apps! All other apps force vsync!

>>109127738
>so turn on VRR
I have many displays supporting VRR, but even with it enabled wayland (by design) introduces an extra frame of input lag.

>>109127767
>their whole issue is they run on dogshit hardware from 15 years ago
No! This is an issue of protocol! Even on the beefiest, newest CPUs, with 5000$ dedicated GPUs, this is still a problem! On my desktop I have an AM5 cpu, running at 5GHz with 16 cores, with 32 gigs of ddr5 ram. It does anything I want and compiles stuff very quickly. Not poor! Not ancient hardware! But because I'm running Wayland, I will ALWAYS DEAL WITH ONE FRAME OF LAG.

I also have a crappy intel celeron laptop that I use exclusively for ssh. It runs plasma identically. One frame of forced input lag. Nobody on older hardware is struggling to run KDE, it's remarkably light given it's complexity. But because Wayland introduces input lag, as it is exactly designed to, this is always an issue.

This is not a "KDE doesn't have this issue". KDE also waits for the entire frame to be rendered before updating the contents of any window. Windows cannot update while the screen is drawing content, by design the window submits its contents to the compositor which will update it ON THE NEXT FRAME. This is a bragged about feature of the protocol which is very explicit. This is functioning as intended and happens using all Wayland compositors. It is not specific to any desktop. And the tearing protocol introduced as a fix only works in fullscreen apps.

GTK is a joke

>screen tearing is good actually
What the fuck is wrong with x11niggers?

>>109127834
>how every project that is not explicitly right wing will become left wing.
not really, many projects that are not infested with mentally ill rightards or leftards are in a better shape. Normally sane humans will be more "right leaning" because leftism is a literal mental illness, while the right wants to be the "based virtuous trad" side but they're too retarded and keep falling for jewish schemes. Most devs and tech people will be more "left leaning" because they spent many time in unnatural environments and have some kind of autism.

People should understand that the internet is not serious business, and it's an intersection between all of the different cultures and views, open source should be about making better software, let the patches be sent from satan himself.

And those trannies that infest projects can easily be told to fuck off and they have no counter attack except whining about it on their echo chambers, but modern castrated men are a bunch of conformist pussies. Just don't be retarded like the xlibre guy and publicly wage war on them, it will only irritate SJWs and other troons and they have enough time to be an annoyance, while other sane people will try to stay afar from this mess.

How do I get my mpv scripts that uses x11 to work then?

function copyPath()
  local uri = mp.get_property("path")
  local pipe = io.popen("xclip -silent -in -selection clipboard", "w")
  pipe:write(uri)
  pipe:close()
  mp.osd_message("Path/URL copied!")
end

-- mp.register_script_message("copy-path", copyPath)
mp.add_key_binding("ctrl+SPACE", "copy-path", copyPath)

>>109131218
don't spawn xclip. use mpv native clipboard:

mp.set_property("clipboard/text", string)

>>109119992
Looks like I won't be using XFCE moving forward. Oh well. Gayland for the Gayman.

>>109131913
This is AI imagination.

>>109127442
quit larping, quit chimping out and get a job already.

>>109130275
they're running on ancient hardware, pay attention to these X11 v. Wayland threads and they'll openly admit to using 10+ year old iGPUs when they complain about shit like this