|
| ▲ | Qwertious 7 hours ago | parent | next [-] |
| "The devs of x11" is a wide category, considering how many X11 devs weren't even born when X11 was first written. Plenty of X11 devs objected to Wayland and tried to patch X11, but when half the devs decide they want to write a replacement and put the original into maintenance-mode, there's not much you can do. |
| |
| ▲ | bigyabai 6 hours ago | parent [-] | | > there's not much you can do. You could fork it. X11 hasn't shipped a major release since 2005, the likelihood of a complete overhaul making it upstream was slim to none even in 2009. X11 developers were better-off focusing on stability, and the Wayland devs moved on. There was no conspiracy to kill either project. | | |
| ▲ | ablob 32 minutes ago | parent [-] | | Forking a project when the issue is that half of the staff left the project does nothing to alleviate the staffing issue, does it? |
|
|
|
| ▲ | PunchyHamster an hour ago | parent | prev | next [-] |
| and failed to learn any lesson from X11 |
|
| ▲ | vidarh 7 hours ago | parent | prev [-] |
| Yeah, no, the X11 devs made pretty much all the wrong tradeoffs for me. |
| |
| ▲ | nixosbestos 7 hours ago | parent | next [-] | | K bro. K. | |
| ▲ | bigyabai 6 hours ago | parent | prev [-] | | I wonder why Valve disagrees. | | |
| ▲ | yjftsjthsd-h 4 hours ago | parent [-] | | Valve ships a Wayland compositor that just runs XWayland for apps and doesn't even expose the Wayland socket by default. I'm really not sure how we're supposed to count that. | | |
|
|
