3 ms·

"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 tri

"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 10mo ago
> 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 10mo ago
  Forking a project when the issue is that half of the staff left the project does nothing to alleviate the staffing issue, does it?
  - pjmlp 10mo ago
    Isn't that the greatness of FOSS over commercial software that keeps being spoken about?
  - cycomanic 10mo ago
    So what is it, in one comment you say there were plenty of x11 devs who objected to wayland (please name and show the posts) and on the other hand you say there were not enough to keep an xorg fork going? People are arguing that fixing the issues in X11 would have been much easier and less work than making wayland. So why could those half of x11 developers who left make wayland while the other half that was left over could not even make one release?
- deleted 10mo ago
  [deleted]