4 ms·

lol you need this which is 40k lines of code https://github.com/swaywm/wlroots.git https://github.com/swaywm/wlroots.git only 500 lines of code (plus 40k but w

by rain1 8y ago

lol you need this which is 40k lines of code https://github.com/swaywm/wlroots.git https://github.com/swaywm/wlroots.git only 500 lines of code (plus 40k but whose counting)

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 ago
  hate that rude thing people do where they mimic you. Don't do that.
  - zaarn 8y ago
    It'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 ago
  The reasonable comparison would be with xlib. The xserver code is all about the hardware drivers.
  - Sir_Cmpwn 8y ago
    Actually, 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.
rain1 8y ago
edit: actually it's double that. did an actual count instead of trusting the incorrect info in the readme.
- Sir_Cmpwn 8y ago
  Assuming you did some kind of primitive `find . -name "*.c" | wc -l` kind of operation to arrive at this number, you also got all of the rootston code. Rootston is a test compositor we use for working on wlroots but it's not actually included in the final wlroots package.

by rain1 8y ago

lol you need this which is 40k lines of code https://github.com/swaywm/wlroots.git https://github.com/swaywm/wlroots.git only 500 lines of code (plus 40k but whose counting)

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 ago
hate that rude thing people do where they mimic you. Don't do that.
- zaarn 8y ago
  It'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 ago
The reasonable comparison would be with xlib. The xserver code is all about the hardware drivers.
- Sir_Cmpwn 8y ago
  Actually, 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.

rain1 8y ago

edit: actually it's double that. did an actual count instead of trusting the incorrect info in the readme.

Sir_Cmpwn 8y ago
Assuming you did some kind of primitive `find . -name "*.c" | wc -l` kind of operation to arrive at this number, you also got all of the rootston code. Rootston is a test compositor we use for working on wlroots but it's not actually included in the final wlroots package.