Date: Thu, 21 Dec 2017 02:30:09 +0100 From: Sid <sid@bsdmail.com> To: freebsd-ports@freebsd.org Subject: Re: Vote: making wayland=on default Message-ID: <trinity-6635ffdc-1c3e-4074-ac59-a97fa84e1b4d-1513819809216@3c-app-mailcom-lxa12>
next in thread | raw e-mail | index | archive | help
Wayland should not be mixed in with other code like gtk3, gtk2, gnome related programs. This will immediately create bloat. Wayland does remove a lot of unneeded obsolete code that is in Xorg, that is put in there by principle, and not much else. If gtk creeps into Wayland, those benefits will be lost. The current eagerness about wanting Wayland is centered around gtk. This will quickly harm the project. Wayland should work on top of xlibs that are not obsolete. Wayland shouldn't be made the default until small window managers like antiwm, blackbox, bspwm, ctwm, cwm, i3, jwm, qtile, vtwm and others like this work on it. It should also work on fluxbox and enlightenment first. Wayland on FreeBSD shouldn't be centered around GNU, gtk or Gnome. I would say make a Wayland-gtk package offshoot, but this will also quickly ruin things. Wayland should stay clean, and allow modular components on top of it, that don't spread out bloat dependencies out. Wayland should keep the same habit as Xorg, with the exception of keeping obsolete hardware code.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-6635ffdc-1c3e-4074-ac59-a97fa84e1b4d-1513819809216>