4 ms·

Is this something where it would be helpful if the Linux (environment) developers worked together? Like the (graphics) kernel, GTK, KDE, Wayland, … guys all in

Is this something where it would be helpful if the Linux (environment) developers worked together? Like the (graphics) kernel, GTK, KDE, Wayland, … guys all in one room (or video conference) to discuss requirements iron out one graphics architecture that is efficient and transparent? I think it’s good that different graphics systems exist but it feels unnecessary that every team has to make their own discoveries how to handle the existing pieces. If work were coordinated at least on the requirements and architecture level then I think a lot of synergies could be achieved. After that everyone can implement the architecture the way that works best for their use case, but on some common elements could be relied on.

rawoul 3y ago
They are: https://indico.freedesktop.org/event/4/ https://indico.freedesktop.org/event/4/ https://emersion.fr/blog/2023/hdr-hackfest-wrap-up/ https://emersion.fr/blog/2023/hdr-hackfest-wrap-up/ https://gitlab.freedesktop.org/wayland/wayland-protocols/-/wikis/meetings https://gitlab.freedesktop.org/wayland/wayland-protocols/-/w... ...
jdub 3y ago
They do, it's just not hugely visible. Two great conferences where some of that work happened were linux.conf.au and the Linux Plumbers Conference.
dontlaugh 3y ago
That’s exactly how Wayland came to be.
BearOso 3y ago
That's exactly what happened. This is the original intent for subsurfaces. A bunch of Wayland developers got together and wrote the spec a long time ago. The only thing happening now is Gtk making use of them transparently in the toolkit. Subsurfaces didn't have bug-free implementations for a while, so maybe some people avoided them. But I know some of us emulator programmers have been using them for output (especially because they can update asynchronously from the parent surface), and I think a couple media players do, too. It's not something that most applications really need.

rawoul 3y ago

They are: https://indico.freedesktop.org/event/4/ https://indico.freedesktop.org/event/4/ https://emersion.fr/blog/2023/hdr-hackfest-wrap-up/ https://emersion.fr/blog/2023/hdr-hackfest-wrap-up/ https://gitlab.freedesktop.org/wayland/wayland-protocols/-/wikis/meetings https://gitlab.freedesktop.org/wayland/wayland-protocols/-/w... ...

jdub 3y ago

They do, it's just not hugely visible. Two great conferences where some of that work happened were linux.conf.au and the Linux Plumbers Conference.

dontlaugh 3y ago

That’s exactly how Wayland came to be.

BearOso 3y ago

That's exactly what happened. This is the original intent for subsurfaces. A bunch of Wayland developers got together and wrote the spec a long time ago. The only thing happening now is Gtk making use of them transparently in the toolkit. Subsurfaces didn't have bug-free implementations for a while, so maybe some people avoided them. But I know some of us emulator programmers have been using them for output (especially because they can update asynchronously from the parent surface), and I think a couple media players do, too. It's not something that most applications really need.