5 ms·
TinyWM also needs all of this code: https://cgit.freedesktop.org/xorg/xserver/ https://cgit.freedesktop.org/xorg/xserver/ ~500,000 lines of code that wlroots
by Sir_Cmpwn 8y ago
TinyWM also needs all of this code:
https://cgit.freedesktop.org/xorg/xserver/ https://cgit.freedesktop.org/xorg/xserver/
~500,000 lines of code that wlroots does not depend on, but who's counting.
- rain1 8y agohate that rude thing people do where they mimic you. Don't do that.
- zaarn 8y agoIt's a very effective way to show that the argument you just made can be easily turned around and at the same time mocks the argument or declares it silly. It's not really rude but rather a pointer that the argument made is not standing on very solid legs.
- deleted 8y ago[deleted]
- upofadown 8y agoThe reasonable comparison would be with xlib. The xserver code is all about the hardware drivers.
- Sir_Cmpwn 8y agoActually, the repository I linked to does not do much more driver stuff than wlroots does. The xorg drivers are maintained in separate trees: https://cgit.freedesktop.org/xorg/ https://cgit.freedesktop.org/xorg/ Most modern xorg drivers depend heavily on mesa to do the heavy lifting: https://cgit.freedesktop.org/mesa https://cgit.freedesktop.org/mesa wlroots depends on mesa as well. xorg-server does do more things than wlroots, but it's mostly legacy stuff. In terms of features anyone wants from a modern display server, they're pretty close. wlroots is repsonsible for spinning up an EGL context, talking to libinput, configuring DRM and KMS display resources, allocating GPU resources with GBM, negotiating pixel buffers with clients, etc, all things that xorg-server is doing for TinyWM.