@dd56@futurology.today to Linux@lemmy.mlEnglish • 5 months agoThoughts on this?futurology.todayimagemessage-square42arrow-up10arrow-down10
arrow-up10arrow-down1imageThoughts on this?futurology.today@dd56@futurology.today to Linux@lemmy.mlEnglish • 5 months agomessage-square42
minus-squarefrankfurt_schoolgirl [she/her]linkfedilinkEnglish0•5 months agoI’ve been using Wayland for 5 years. There were a few bugs in the beggining, but now it works great. These threads are such a waste of time. I have over 100 confirms X11 developments That’s great dude. Why don’t you go maintain it then, apparently nobody else wants to: https://www.phoronix.com/news/RHEL10-Removing-X.Org Wayland took too long Look up how long btrfs has been in development, or at audio subsystem churn. These things take time, because it’s mostly volunteers working on them. Systemic complexity has doubled in the last two years What does this even mean? Mir was better It turns out the Canonical dumping random stuff over the wall is not the same as creating a legitimate open source community around a project. Unfixable amount of race conditions As if there’s never been a synchronization bug in X… But also System76 and others are writing Wayland compositors on Rust anyway.
I’ve been using Wayland for 5 years. There were a few bugs in the beggining, but now it works great. These threads are such a waste of time.
That’s great dude. Why don’t you go maintain it then, apparently nobody else wants to: https://www.phoronix.com/news/RHEL10-Removing-X.Org
Look up how long btrfs has been in development, or at audio subsystem churn. These things take time, because it’s mostly volunteers working on them.
What does this even mean?
It turns out the Canonical dumping random stuff over the wall is not the same as creating a legitimate open source community around a project.
As if there’s never been a synchronization bug in X… But also System76 and others are writing Wayland compositors on Rust anyway.