5 ms·
You can’t really claim that Wayland has been in the works for x and x years, when such a hugely critical piece of the ecosystem needs network effect to strive.
by kaba0 5y ago
You can’t really claim that Wayland has been in the works for x and x years, when such a hugely critical piece of the ecosystem needs network effect to strive. And I believe wayland has just recently got the critical mass to become the next X, but not getting it sooner is not due to its lack of technical merit.
- smoldesu 5y agoThe issue is that Wayland isn't a replacement for X. It's become it's own thing entirely, with it's own goals and conflicts with the xorg ideology. On top of that, it doesn't have feature parity with the window server on Windows and certainly doesn't approach the capability of Quartz (and likely never will, judging by it's core values). This puts it in an awkward spot: certain developers are begging users to switch to Wayland despite the fact that it only works with two and a half DEs, while other developers are pledging to never transition their software in the first place. Wayland's own development is constantly taking forwards and backwards steps in ways that are scaring users (like myself) away from using it. This is the part where I'd usually give credit to the developers for not turning it into a GNOME-first utility, but even that's untrue as the only "complete" implementation is Mutter. At this point I've conceded that I will use x11 until I die. I will write software for x11 until I stop writing software. Yes, it is miserable, but it's never failed me and there has never been any "politics" ruining it. There's no wlroots to fuck around with to get certain basic features working. There's no xWayland to scream at when my software doesn't "just work". The whole thing is so disappointingly ironic that I can't help but ignore it's development.
- throwaway82652 5y agoYou will be miserable and waiting forever because what you want is impossible for all practical purposes. Feature parity is a red herring when some newer features just can't be done properly on X. The "xorg ideology" is to basically not have security on anything and to consider GPUs to be an afterthought, as stated by a parent comment. From a user perspective, this situation is untenable and yet will never actually improve because doing so would break the protocol and all the clients. I've spoken to some of the other DE developers and pretty much all of them have said to me the only reason they don't want to move away from X is because they lack the manpower to do it. Also, the reason there's no "politics" anymore is because most of the developers have moved on to Wayland. There were quite a few flame wars on the X mailing lists back in the day. You can probably blame some of that for the existence of Wayland, which should actually have less politics because multiple groups are no longer fighting for what to put in the one centralized X server. The one area where there was activity, and arguments were popping up again was... you guessed it, Xwayland, but they solved that by bring it into its own release cycle away from the rest.
- rbreaves 5y agoThe “security” of wayland is a bit of an illusion imo. I’ve already seen a user pick it apart awhile ago. Regardless I don’t what they’re trying to do, but they do need to add in a proper method for granting higher privileges to apps to have more access to Wayland in the same way macOS grants access to Remote Desktop apps.
- throwaway82652 5y agoNo, you haven't. I'm fairly certain I know a blog article you're referring to and that article is a load of nonsense. I can debunk any claims you might remember. The security isn't an illusion, it was designed to fix very real and known problems that exist in X11 and likely won't ever get patched out from X11. At least in GNOME and KDE, there is a proper method for granting higher privileges, that method is the xdg portal API. I don't know where people are getting this idea that the method doesn't exist, it has existed for quite some time now.
- smoldesu 5y ago> I can debunk any claims you might remember. Listen, I don't care who you are or what your agenda is, but a line like this just confirms my suspicions that you're trolling. Quit it, please. Your constant bickering with anyone who disagrees with you is undermining the site's values of gratifying intellectual curiosity. It kills fruitful conversations, makes it harder to take your arguments in good faith, and colors your stance as simply contrarianism. I'm going to continue ignoring your comments if this is the basis of your conversation on this site.
- throwaway82652 5y agoMy agenda is to explain how this stuff works to stimulate intellectual curiosity. That's literally all there is to it. I've seen a number of wrong claims posted about this in the past, if you can remember any of the claims I'll address them directly and we can have a fruitful conversation about it. If you feel that examining past claims under a critical light is "trolling" and "kills fruitful conversations" then I don't know why you're even bothering to discuss this, please just let me address the claims made by the other commenter. Feel free to ignore me.
- throwaway82652 5y agoTo add to this, there was a pretty large consensus among X developers probably 10-15 years ago that X was not a viable future direction and it needed to be abandoned. The alternative to Wayland (or Mir, or whatever) is not going back to X, the alternative is do nothing and bitrot sets in and you just don't have a functioning desktop anymore after a while. I wouldn't even say the network effect matters that much, a huge part of the work has been disentangling the drivers from X. It's not very visible work to userspace developers but it's probably even more important than any work on the window system. The DRM/KMS/GEM subsystem is now widely adopted for kernel drivers, that work took a long time but doing it correctly means userspace is now freed up to implement any windowing system they want without having to deal with the driver mess caused by X.