411–420 of 518 posts
One thing that a great majority of commenters here seem to be missing is that Wayland's issues that make it unsuitable to replace X Windows will not just be ironed out in a couple of years (at least not in a way that would be an improvement over X), because it is flawed by design. The thing is, Wayland developers do not want you to take screenshots or automate input events (injection and interception). Those are both…
Earlier quoted context omitted.
While I generally understand your sentiment, I can't see how does it apply to Wayland in particular. You can replace Wayland with X11 and basically make the same argument. You can implement Wayland compositor on top of X11 protocol if you wish. You can also implement X11 server on top of Wayland protocol (and that's actually already done and widely used, called XWayland). Given the oddities and architectural baggage…
XWayland isn't a normal Wayland client - it requires special assistance from the compositor. In particular, the compositor acts as the X window manager and there's a special interface between it and XWayland on the Wayland side to make everything work. I don't think it's possible to even implement something like XWayland as an ordinary Wayland client. By design, ordinary Wayland windows are not permitted to know or c…
Basically any sensible Wayland compositor you may want to use on your desktop already has XWayland properly integrated. If one of them drops it, you can switch to a more sensible one.
Earlier quoted context omitted.
Well that's because if you click on that link from HN it uses the referrer details provided by your browser to show quite a rude message and picture ;)
Wow, never seen this before. I don’t get the animosity HN sometimes revives. I don’t really care for startup stuff and I just ignore it, but the average level of discussion here is extremely high. One of the best in the web. Compare HN to Twitter or Reddit and it’s night and day, and it has been for years.
Earlier quoted context omitted.
Maybe a dumb question but why do people want to use Wayland if it's that horrible?
X.org is more horrible and also impossible to maintain. It would have been given the boot over a decade ago except for the fact that AMD/then ATI and Nvidia only supported X and video drivers were incorporated into X directly. There was a big push starting in ~2008 where AMD started open sourcing their drivers. Infrastructure started developing in the kernel where it makes sense instead of in X. Now we've reached the…
I would have slightly preferred AMD, but I wanted an i9 in a laptop that had good Linux support, and so nVidia was all I could get (XPS15).
One thing that a great majority of commenters here seem to be missing is that Wayland's issues that make it unsuitable to replace X Windows will not just be ironed out in a couple of years (at least not in a way that would be an improvement over X), because it is flawed by design. The thing is, Wayland developers do not want you to take screenshots or automate input events (injection and interception). Those are both…
You cannot take screenshots with wayland??
Earlier quoted context omitted.
Thank you, I hadn't heard of it before so I'll check it out! I'm not optimistic about Wayland, since early on they decided not to use an extension language, and that's not something you can have a change of heart about later, and then just nail onto the side. It would be interesting to see how Arcan uses L ua, which is a great language for that kind of stuff. It's a lot smaller and sleeker and better designed than Ja…
I get paid to work on Arcan so I don't think factorio would have that big of an impact ;-) The initial choice of Lua for Arcan was based on its use, at the time (2004-2005ish), in World of Warcraft. The UIs that people were hacking together in WoW even with little to no serious programming experience was way more advanced than what would ever be needed for desktop interfaces so it seemed like a good fit. Even for oth…
Earlier quoted context omitted.
Windows and OS X are well-known for constantly deprecating APIs and replacing them with new ones. So clearly the best way to compete with them is to insist on dogmatic adherence to 30-40-year old APIs that are known to be horrible matches for how modern software stacks (including competitor OSes) actually work.
Windows supports core APIs for longer than Linux, or in fact, X11 exists. It's actually possible (and was demonstrated) to upgrade from 1985 Windows 1.01 all the way up to 32bit Windows 10 and run windows 1.01 application without changes . Arguably backward compatibility is the true reason how MS got to dominate OS market - you had good chance your software was just going to work on new OS version.
Earlier quoted context omitted.
How long did it take to get multiple monitors working with xrandr, again?
Multi monitor display worked perfectly for long time, long before "it works on intel, let's call it new standard" crew decided that flat shared framebuffer is the only way to go (apparently because of compositors and nothing else), something that also broke support for multi-gpu and especially heterogenous multi-gpu.