4 ms·
I agree. On one hand I can understand the need to shrink code, focus on the core functionality etc..., but on the other hand X has e.g. "xset" and "xbindkeys" w
by zepearl 6y ago
I agree. On one hand I can understand the need to shrink code, focus on the core functionality etc..., but on the other hand X has e.g. "xset" and "xbindkeys" which can be used for all X-desktops (or "Window Managers" or however they're called). With wayland each single desktop environment has to re-implement all that functionality => looks like wasted effort to me - the modularity (from the point of view of functionality) of X is lost in Wayland.
- the_why_of_y 6y agoOne of the innovations since the 1980s when X was designed are shared libraries, so you can have libweston and wlroots now https://github.com/swaywm/wlroots https://github.com/swaywm/wlroots
- frank2 6y agoX11 used shared libraries since its beginning in the 1980s.
- the_why_of_y 6y agoSunOS paper about shared libraries, 1987 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.9514 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.9... SunOS 4.0 lists "dynamic linking" as new feature, released 1988 https://en.wikipedia.org/wiki/SunOS https://en.wikipedia.org/wiki/SunOS AT&T System V Release 3 got shared libraries in 1986 https://en.wikipedia.org/wiki/System_V_Release_4#SVR3 https://en.wikipedia.org/wiki/System_V_Release_4#SVR3 While the first X11 release was in 1987, the fundamental architecture was designed already since 1984, and this architecture includes a heavyweight server that implements things that in most other window systems are done client-side.