upvote

points

by Ciantic4 hours ago |
comments
upvoteby sandreas2 hours ago|
next
[-]
For everyone interested in Avalonia's Linux / Wayland strategy:

https://avaloniaui.net/blog/bringing-wayland-support-to-aval...

reply
upvoteby MikeCodesDotNET2 hours ago|
parent|
[-]
We’re actively working on Wayland support for Avalonia 12. While we considered dual licensing it, we ultimately decided to keep things simple and make it MIT licensed.
reply
upvoteby Pay083 hours ago|
prev|
next
[-]
Not to mention that there's no clear documentation for this anywhere. A while ago I was attempting to debug some Wayland-specific issues with a graphics library, it turns out the issue was that the little documentation there was, was wrong about what is and isn't nullable.
reply
upvoteby OtomotO3 hours ago|
parent|
[-]
I found https://wayland.app/protocols/ very helpful so far.

That and studying smithay code.

reply
upvoteby Pay082 hours ago|
parent|
[-]
That was the documentation with the incorrect nullability I was referencing.
reply
upvoteby shevy-java2 hours ago|
prev|
next
[-]
Wayland is a mess.

Perhaps https://github.com/X11Libre/xserver can revive the older ecosystem. Almost nobody writes for wayland. About two years ago I tried to switch, then gave up when I realised how many things are missing on wayland. And then I noticed that barely anyone wrote software for wayland. It feels like a corporate advertisement project really. GNOME and KDE push for wayland now.

reply
upvoteby LeFantome2 hours ago|
parent|
next
[-]
What does “nobody writes for Wayland” mean?

If you write software using GTK, Qt, or FLTK then you are writing Wayland software.

The majority of Linux desktops are Wayland at this point. Nobody writes software for them?

The Steamdeck uses gamescope which is Wayland. GNOME, COSMIC, Budgie, Niri, and Hyprland are not just Wayland but Wayland only. KDE will be Wayland only soon. Cinnamon is switching to Wayland. XFCE is writing a Wayland compositor.

What percentage of Linux desktop users are not using one of the above? 10 at most?

reply
upvoteby noselasd1 hours ago|
parent|
next
[-]
It just means "noone" uses the wayland APIs directly, but instead they leave the wayland complexity to GTK,Qt or FLTK, and they call their app a Qt app, not a Wayland app.
reply
upvoteby simonh24 minutes ago|
parent|
[-]
Was X11 any different in practice? Apart from ancient legacy stuff like XTerm. It would be like writing a Mac application in Quartz directly.
reply
upvoteby 1 hours ago|
parent|
prev|
[-]
deleted
reply
upvoteby Gigachad1 hours ago|
parent|
prev|
next
[-]
You have to go quite out of your way to not use Wayland. Pretty much all mainstream distros switched over long ago. This just feels like the systemd drama restarted. Some will complain and hold on to the past for as long as they can but the rest of the world moves on. Wayland is the better choice today.
reply
upvoteby eikenberry1 hours ago|
parent|
prev|
[-]
I think Wayland is basically waiting for a higher level abstraction to fully replace X11, at least for the desktop. I'm currently playing with the River Wayland compositor (https://codeberg.org/river/river) which separates the window manager from the compositor and I think it could fill this gap left in the transition. Not as sure about non-toolkit (gtk,qt) application development...
reply
upvoteby audidude3 hours ago|
prev|
[-]
[dead]
reply