Looks like the discussion centers around a claim that some sort of specification that is not being properly implemented/obeyed. I don't see many people disputing that claim.

There is a pro-wayland side that apparently thinks setting wayland as the default is more important than technical issues because it "signals" to people that wayland is the future. It's not even a quantitative/qualitative dispute. Their goals have an evangelical component. ALL MUST USE WAYLAND. GLORY TO THE FUTURE.

There was this fun tidbit though if you want to test it out.

3 members found this post helpful.

Flip-flop.
The full story can be found at, https://www.phoronix.com/news/SDL-3....efault-For-Now

1 members found this post helpful.

I love running comparative benchmarks, but the results change with every patch level.

That sigh really didn't have anything to do with neither you nor your post... just the situation at hand.

With that cleared, carry on!

On the same day phoronix posted about sdl3+wayland he also posted about EXT2 support in Linux 6.9. Time to move on to the next crisis.


WE ARE ALL DOOMED AAAAHHHHHHHH

1 members found this post helpful.

EXT2 is not gone, it is still supported by usage depreciated. IF anyone wants to do the coding to adjust the drivers and defaults for EXT2 those drivers could be rescued, it would not even be hard. But EXT4 handles EXT2 file systems just fine, so do we really NEED ext2 drivers?

Will be able to live just fine without ext2 drivers as long as we have a creation tool and existing drivers will continue to make that file system work. Right now they coexist just fine, and there is time to plan a strategy in case ext2 support goes away.
We live just fine with X.Org and Wayland coexisting, and we have lots of time to plan a strategy for when one goes away. If ever. X.Org is not depreciated!



There are several things going on in the world that justify anxiety, if not panic: X.Org and ext2 are not among them.

1 members found this post helpful.

Well I can't help but contribute to this tangent - but isn't ext3/4 (maybe not 4), but I know ext3 is backwards compatible with ext2? While I don't use ext2 I am on the fence on it being removed, just like how maybe even fat16; hopefully there isn't any talk yet to remove or deprecate because I am sure there is a use-case; and we know fat32 can never be deprecated due to UEFI. I would be interested to know if JFS is going to be on the chopping block, I moved away from JFS solely to XFS, and I could see a better reason because JFS hasn't been updated in 14 years, and probably has a very low number of usage, probably even less than one of the reiser(3 or 4) , but it also makes sense why reiser is getting the boot.

1 members found this post helpful.

FYI: I just pulled updates to my system today, and received new versions of X.org server.
Just in case you thought that was no longer a thing.....

For those Nvidia users experiencing Wayland remorse, help is on the way:
https://9to5linux.com/developer-expl...wayland-issues

1 members found this post helpful.

I am sure you mean "deprecated" in the sense of
obsolete and on-its-way out.
I haven't gained much appreciation for Wayland.
It's kinda cute but it's about as buggy as cockroach soup.
I have yank'd out my nvidia card and have a couple of inexpensive portable usb-c monitors direct to motherboar in my 4-monitor system that can go on the road with me and my luggable box.

Wayland is imprecated here pretty much like the Rev Dr Gates , and X.org on Slackware does not suck.

1 members found this post helpful.

Well, if Slackware will continue to use KDE as the main desktop, Wayland will become default with KDE6. That's ofcourse unless Slackware decide to go against the choice of the distributed package, which it tends not to do.

This still going on? I think it's been originally directed at me, so..
KDE may use wayland as default or not, I don't use KDE since 4.3 or something like that, so it's really none of my concern.
Blackbox on X will probably still work fine until X is no longer maintained, regardless of what KDE does.

But I guess if Xfce4 will work on optional wayland backend, as was announced, then I will probably try it out.
And basically my only point against wayland was:
If wayland deskops must use a framebuffer device and the nvidia driver does not support specifying EDID on kernel command line, then the thing's basically useless for me.
I mean WTH in order to run wayland compositor I must now either use nouveau and forget about hardware video decoding, or else downgrade desktop resolution from 1680 to 1024 because edid binary is unsupported still.
No idea how it takes so long for them (nvidia) to implement this basic functionality in ther framebuffer driver, since nouveaufb has had it for many years.
That's pretty much it. Apologies again for any foul language.

1 members found this post helpful.

Michael just made a Wayland/Xorg gaming performance test under Plasma 6: https://www.phoronix.com/review/kde-plasma-6-amd-gaming

In 2007 I was using the Ion3 window manager and learning Haskell. At the time there were signs that the future of Ion3 was uncertain and I started looking for an alternative tabbed WM. I discovered that the Haskell community had started developing a dwm clone, a tiling but extendable WM called xmonad, so I joined them and started contributing documentation while learning the code base and xlib. In a few weeks I acquired enough familiarity with xmonad and xlib (the Haskell bindings but also the Haskell foreign function interface) and I started coding: at first, just to get used to X11, I coded a small status bar (I called it xmobar), then I started contributing to the xmonad extension library: I wrote a command prompt, decorated tabbed and floating extensions and so on. I was basically recreating Ion3 on top of it...At the time I think that I and David Roundy were among the main developers.

Then some discussion started on how to modify the core of xmonad in order to simplify the coding of the extension library. Moreover we wanted to have some more sophisticated workspace support. As a result I was kicked off the project -- my commit access removed overnight -- and David left shortly after, and so we started a fork for our personal use. David created a new data model for managing windows and workspaces and I ported all we needed to the new model. Later David lost interest for tiling WMs and started working on something different, but I kept maintaining my fork, which I'm still using today.

When I moved from slakware 32 to slackware 64,in late 2019, I discovered many bugs in the Haskell bindings to xlib, bugs that were not properly fixed by xmonad which was using exception handling to cover them (maybe something have changed in the meantime, but I didn't check). So I went back to writing my bindings, checking for null pointers and so on.

That was easy because xlib is stable and very well documented, so even a non professional coder like me can maintain a home brewed WM with little effort.

The idea of the X11 obsolescence started frightening me a few years ago, when I saw Wayland was gaining momentum. From time to time I went back to see if, in the Haskell community, something was being planned and maybe done. That always left me worried: the xmonad guys at fist rejected the idea of porting it to Wayland -- an attempt was made but it didn't last very long. Now they are discussing to do the move but Haskell bindings to Wayland and wlroots are still in their infancy -- and maybe the fact that wlroots seems to still be a moving target is slowing the process.

So, a few weeks ago I started studying the possibility of doing the job myself, but I feel completely lost: I couldn't find good documentation and, from reading what I found, I have the impression that writing a compositor is beyond my capability, in terms of understanding how a graphic server works and in terms of time needed to accomplish the goal.

Maybe Wayland is the future and only professional coders should be allowed to write what for my generation was a simple WM and now is a, ehm, compositor. Perhaps I'm bound to stick to the past. But, as h2-1 was pointing out, I do not think this is going to work forever: GTK, QT and other toolkits, which are used in so many application I relay upon, will require me to switch. But I'm old and getting used to a new environment after so many years of being able to take care of my needs will not be a pleasant adventure.

2 members found this post helpful.

I've been through this many times before: APM vs ACPI; OSS vs. Alsa; The time to move over is when you get shoved by your distro of choice. No need to worry.

I'm current resisting using 'ip' over ifconfig, systemd over sysVinit, and Wayland over Xorg. Oh, I'm resisting KDE. The only ones I feel strongly against are KDE, 'ip' & systemd. But change is a part of life. I moaned over uefi, but I got over it. I'm sure you guys will too. It's called inertia, and it's common.

When something with flaws takes over, a torch goes under their behinds to get better or die. That will happen (e.g. zoom over skype) or designers will work around it. And if something fully loses it's dominant spot, it's not inclined to make a return.