Casilda Is A New Project As A GTK4 Wayland Compositor Widget

[access]

RHEL going Wayland only doesn't really matter much because the only groups that use RHEL on desktop are film studios etc who will probably stick on older versions for as long as they can.

What are film studios using RHEL on the desktop for and why would they not want Wayland (the only one with any prospect of HDR support)?

[Quackdoc]

Ah yes, the world-class software architects are visiting Phoronix again to spread their wisdom

considering we still have users who are complaining that wayland is completely and utterly broken for them since they can't fucking configure their bloody peripherals that they could on x11. yes.

the fact that we don't have generic controls for stuff like libinput is so bafflingly dumb highschool kids think it's a <automod thingy> design

[Artim]

It truly must be!! But citation needed...

Why would I when you don't bother proving your poingts either? Beyond some cheapheads that are too lazy adapting anything that's not many years old, just nobody cares about X anymore. Like it or not.

[Artim]

this is no where close to the same situation. I mean, lets say perhaps we learned nothing from the past decade or two of development. the perhaps we could say "well take a look at how long x took". but that's crap. we have learned lots, and we should have learned more. Let's be clear here. The reason why wayland is so stagnant is because everything regarding wayland wayland is a poorly designed. It can take literal years to add something simple as there is an extremely large amount of NIH syndrome going on. We still don't even have a even somewhat universal way to configure libinput for anything that isn't covered by udev rules. Between the fragmentation of portals, protocols, and everything else. Wayland is one of the most poorly conceived ideas that we are now effectively stuck with.

Thanks for making it that obvious that you haven't touched Linux in at least a decade. Wayland is everything but stagnant. It is the default already almost everywhere and it won't even take another decade for X to be ripped out of every distro out there, only leaving XWayland for compatibility with legacy software. That's how Cosmic is being built, that's how Gnome (not entirely sure about Plasma) can be built and how they will be built for Fedora and soon RHEL. Other distros will follow not long after. X is dead, like this fact or not, just accept reality.

[Artim]

What are film studios using RHEL on the desktop for and why would they not want Wayland (the only one with any prospect of HDR support)?

Pretty much all VFX is done on Linux, as they've never used some proprietary and Windows-bound software in the first place, but written their own programs. While I don't know what Britoid was talking about, but my guess is, as those machines will probably not be connected to the internet, but only to each other to make them rendering nodes when they aren't used, OS updates are probably irrelevant to them. Also, HDR support has been a thing for a long time, just not through X, but despite X. They'll probably go the same route.

[Quackdoc]

Thanks for making it that obvious that you haven't touched Linux in at least a decade. Wayland is everything but stagnant. It is the default already almost everywhere and it won't even take another decade for X to be ripped out of every distro out there, only leaving XWayland for compatibility with legacy software. That's how Cosmic is being built, that's how Gnome (not entirely sure about Plasma) can be built and how they will be built for Fedora and soon RHEL. Other distros will follow not long after. X is dead, like this fact or not, just accept reality.

Ah yes, it's progressing so fast that after a decade we can now finally record the desktop without needing to use crap like portals. Still can't create a simple taskbar with upstream wayland either. oh so much progress happening so fast.

[Artim]

Ah yes, it's progressing so fast that after a decade we can now finally record the desktop without needing to use crap like portals. Still can't create a simple taskbar with upstream wayland either. oh so much progress happening so fast.

Actually, not forcing apps to use the xdg-portals for such sensitive tasks like screen recording is a huge step back thanks to progress refusers like you. The point of Wayland is to give all control of those sensitive tasks to the user and preventing apps to use them without the users knowledge. That's what the xdg-desktop-portals are meant for. So compositors will have to force these protocols to behave the same way to not nuke the users security.

And what do you mean with taskbar and why on earth would that be something that needs to be done by the display protocol and not by the DE/WM?

Tl;dr: your whole comment like always lacks any substance and just shows how little you understand the things you talk about.

[Quackdoc]

Actually, not forcing apps to use the xdg-portals for such sensitive tasks like screen recording is a huge step back thanks to progress refusers like you.

you are right, it's a massive step back from insanity.

. So compositors will have to force these protocols to behave the same way to not nuke the users security.

no they wont. There are many possible ways to do this, and that fact that we don't have to deal with cursed portals providers is a great benefit to a lot of people, myself included.

And what do you mean with taskbar and why on earth would that be something that needs to be done by the display protocol and not by the DE/WM?

LXQT is implementing as far as I know, 2 different protocols for this, possibly three. the fact that this is needed is the height of idiocy.

Tl;dr: your whole comment like always lacks any substance and just shows how little you understand the things you talk about.

Just because you lack the ability to understand other people's viewpoints doesn't mean they are bad. It just means you have a deficiency in thought capacity.

[mos87]

The guy's reinvented the X11 tray?

[anda_skoa]

The guy's reinvented the X11 tray?

No, this is about combining the output of two or more processes into one.

Essentially the way every modern web browser works but available to normal application developers.

In case of web browsers one process to provide the main UI (menu, toolbars, etc) and one processes per open tab to provide the content.

Of course the same kind of separation is potentially interesting for other type of applications.
Could be used for more parallelism, isolation, etc.

Server side systems have been using this multi-process architectures for a very long time, this enables UIs to do the same.