What you see is wrong, i'm not telling anyone not to build things. If anything i wrote > i do not mind Wayland existing (even though i see no point in it perso

What you see is wrong, i'm not telling anyone not to build things. If anything i wrote > i do not mind Wayland existing (even though i see no point in it personally) as much as i do not mind Arcan existing - or Qt existing, Gtk3 existing, ZSH existing, Ruby existing and any other project that provides an alternative option to another project. But i also wrote > What i do mind is the manipulation going on to force me (indirectly mainly, through all the efforts going on - yes i know that technically nobody puts a gun on my head) to use Wayland. In other words, build as much as you want, just do not force me to use what you built. If i like it, i'll use it. But that is not what happened with Wayland which is forced to people through other projects. As an example see what KWin's developer said some time ago wrt. to X11 in that they wont accept any fixes or features for X11 and everything new will be for Wayland and even if someone does the work it will not be accepted. That is a clear case of KWin's developer sabotaging X11 in favor of Wayland, not of Wayland having some merits over X11. Others haven't been as out there as KWin's developer, but i wouldn't be surprised that the reason mainline Xorg lies about the display's DPI (this is patched by most distros out there) instead of reporting the real one was those "Xorg developers" who went on to work on Wayland as having this information is enough for toolkits to implement per-display arbitrary scaling support (one of the supposed features Wayland has over X11). As for what i have built, i have built a bunch of stuff, but it doesn't matter since they are irrelevant to this discussion and what i have written. What i'm writing matters and it is enough to stand alone by itself, i do not need to appeal to any authority - be it mine or someone else's.