Originally posted by curfew
View Post
Announcement
Collapse
No announcement yet.
Wayland 1.19 Alpha Released
Collapse
X
-
-
Originally posted by set135
Well, there are a few libraries. libweston and wlroots being probably the most prominent. wlroots lists dozens of projects using it, so the claim that every compositor has its own implementation seems incorrect. What is probably more correct is that the two majors of the linux desktop have mostly gone their own way implementing wayland because they have a large legacy code base.
One major issue is also platform-independence. When each and every window manager has to re-implement abstract crap on their own, they will use whatever is convenient. Right now each and every Wayland compositor is strictly tied to Linux, blocking modern desktops from the BSDs in a brutal way.
If we had a single centralized implementation, it would be trivial to make all DEs platform-independent by porting this single (albeit major) piece of software to FreeBSD or NetBSD or other FOSS operating systems. Since porting code designed for Linux-specific libraries isn't an easy task, you can only imagine the burden on the BSD devs to making even a single desktop environment run smoothly on BSD, and the tears when they have to start all over again to make it happen with another DE again.Last edited by curfew; 22 December 2020, 08:07 AM.
Leave a comment:
-
Originally posted by zxy_thf View PostThis could be a good move, but I'm afraid it's too late now.
If something like libwayland-compositor was proposed and developed 5 years ago, this could end up inside different compositors.
But nowadays since every compositor has its own implementation, this library is pointless. New developers may prefer to fork an existing project and start from there.
Leave a comment:
-
Originally posted by timofonic View PostI think Wayland should adopt the Vulkan approach, not the current one.
- Likes 2
Leave a comment:
-
Originally posted by furtadopires View Post
Agreed
I also said this in the last wayland post.
If something like libwayland-compositor was proposed and developed 5 years ago, this could end up inside different compositors.
But nowadays since every compositor has its own implementation, this library is pointless. New developers may prefer to fork an existing project and start from there.
- Likes 1
Leave a comment:
-
Originally posted by timofonic View PostI think Wayland should adopt the Vulkan approach, not the current one.
I also said this in the last wayland post.
- Likes 2
Leave a comment:
-
I think Wayland should adopt the Vulkan approach, not the current one.
- Likes 3
Leave a comment:
-
Is drag-and-drop working now? Or is that planned for an upcoming release?
- Likes 1
Leave a comment:
-
Another Wayland topic. Everyone, get your bingo cards out of the drawer!
- Likes 6
Leave a comment:
Leave a comment: