4 ms·
It's worth noting this is not the first time that X has become abandonware. It's not even the second time. This is the third time X development has been aband
by hapless 6y ago
It's worth noting this is not the first time that X has become abandonware.
It's not even the second time.
This is the third time X development has been abandoned. And yet, millions of us use X11 every day.
Don't hold your breath for Wayland to replace X11.
- iso8859-1 6y agoI am curious, what are the others? When XFree86 was forked to X.org, is that what you call the first?
- rjsw 6y agoXFree86 was itself a fork.
- na85 6y agoWhat's the difference between X11 and xfree86 (and I guess Xorg)?
- kstrauser 6y agoXFree86 was an implementation of the X11 protocol. X.org is a fork of the XFree86 project (short version: XF86 license changed, and a huge chunk of the core contributors saw that as the final reason to take their work elsewhere).
- jdub 6y agoIf you're talking about forks, they're pretty much the complete opposite of abandonment. Forks exist because people want to work on the code.
- hapless 6y agoIn these cases, forks were deeply interconnected with project abandonment X11 gave us XFree86, because changes to the X386 server weren't being merged. There wasn't much of an alternative to forking. Xorg was forked from XFree86 over a license change, but after the fork, XFree86 died -- its maintainers were unable or unwilling to merge changes or do releases.
- jdub 6y agoThat's a different concept of abandonment to what's happening with the Xorg server code today.