A Wayland Compositor in Minecraft • Hacker News Board

Re: A Wayland Compositor in Minecraft

#81

Post by uecker » Mon, May 25, 2026, 8:34 AM UTC

array_key_first wrote: post #76

tosti wrote: post #73

Earlier quoted context omitted.

There's really no need for any finger-pointing while bragging about features.

It's not bragging - the commenter stated that Wayland has no advantage, which isn't true. It has many features which just are not possible in X. Many of these features are par for the course on Windows and MacOS. They do matter to some people, but not all of course.

It has no fundamental architectural advantages. That some newer features are now only implemented on Wayland makes the situation worse.

Re: A Wayland Compositor in Minecraft

#82

Post by redeeman » Mon, May 25, 2026, 3:14 PM UTC

uecker wrote: post #74

redeeman wrote: post #71

Earlier quoted context omitted.

its not just KDE, its pretty much everyone in the space. I explicitly said im sure some have worse experience with wayland, perhaps read what I wrote? Are you denying wayland is net benefit for the majority?

Yes, I do not believe for a second that wayland is a net benefit for the majority. Every improvement one can have in Wayland could have been implemented in X without breaking compatibility, without causing all the regressions and limitations that are waived away so arrogantly, without fracturing the community, and also ten years earlier.

it couldnt have been done without breaking compatibility. not while actually solving problems.

This is what the actual X developers are saying, which coincidentally are also the wayland developers, and several downstream projects like gnome/kde.

SOME of the issues could have some solutions implemented, but far from all. just look at xlibre, before they even came to functionality they broke stuff in changing things - which they admittedly have fixed for now, but lets follow that and see how far they go.

on one side we have all the developers of Xorg etc saying one thing, and you(and others, that I presume are not involved with Xorg) saying another.

Wayland could have also been 10 years earlier, but because most people just coasted on xorg, which I agree has been kinda reasonable, nobody really took it serious until recently.

you are also moving the goalpost in regards of net benefit. Just because SOME things could be done in X, doesnt mean its not also a benefit to have it in wayland.

Re: A Wayland Compositor in Minecraft

#83

Post by array_key_first » Mon, May 25, 2026, 7:29 PM UTC

uecker wrote: post #81

array_key_first wrote: post #76

Earlier quoted context omitted.

It's not bragging - the commenter stated that Wayland has no advantage, which isn't true. It has many features which just are not possible in X. Many of these features are par for the course on Windows and MacOS. They do matter to some people, but not all of course.

It has no fundamental architectural advantages. That some newer features are now only implemented on Wayland makes the situation worse.

No, it definitely does. Features like disparate refresh rates are very difficult to implement in X11 so they weren't. Bear in mind we have exactly one modern X implementation, x.org, and it's very hard to add new features. The codebase is old and complex.

The main strength of Wayland is that it encourages competing implementations. There are many Wayland compositors. That might be interpreted as a downside, but what it allows is innovation and incremental improvement. Something that was just not happening with X.

You could argue that it could have happened with X. What you can't argue is that it did, because it didn't and that's not up for debate. That's just the truth.

And, it doesn't even matter anymore, because x.org isn't being actively developed in any meaningful sense anymore.

Re: A Wayland Compositor in Minecraft

#84

Post by mghackerlady » Tue, May 26, 2026, 2:29 PM UTC

arikrahman wrote: post #80

mghackerlady wrote: post #50

Earlier quoted context omitted.

If it handles text, it is in the realm of things you can reasonably prefer to do in emacs

Heck, I'll let AI hack it apart and turn it into an NLE video editor or 3D modeler if I could.

No need, just use exwm or whatever the current wayland equivalent is and run shotcut or blender in it

Re: A Wayland Compositor in Minecraft

#85

Post by uecker » Tue, May 26, 2026, 7:53 PM UTC

array_key_first wrote: post #83

uecker wrote: post #81

Earlier quoted context omitted.

It has no fundamental architectural advantages. That some newer features are now only implemented on Wayland makes the situation worse.

No, it definitely does. Features like disparate refresh rates are very difficult to implement in X11 so they weren't. Bear in mind we have exactly one modern X implementation, x.org, and it's very hard to add new features. The codebase is old and complex. The main strength of Wayland is that it encourages competing implementations. There are many Wayland compositors. That might be interpreted as a downside, but what…

No, I don't think this is true and just the usual nonsense used as justification. Some people continue to develop X, so I hope this is sufficient that I can continue to avoid Wayland.

Re: A Wayland Compositor in Minecraft

#86

Post by redeeman » Wed, May 27, 2026, 8:15 AM UTC

uecker wrote: post #85

array_key_first wrote: post #83

Earlier quoted context omitted.

No, it definitely does. Features like disparate refresh rates are very difficult to implement in X11 so they weren't. Bear in mind we have exactly one modern X implementation, x.org, and it's very hard to add new features. The codebase is old and complex. The main strength of Wayland is that it encourages competing implementations. There are many Wayland compositors. That might be interpreted as a downside, but what…

No, I don't think this is true and just the usual nonsense used as justification. Some people continue to develop X, so I hope this is sufficient that I can continue to avoid Wayland.

so what you're basically saying is that with the exception of a very few individuals working on xlibre, the developers of xorg, KDE, GNOME and several others are essentially lying about the feasability of continuing with xorg? that, or too incompetent to make the same realization you did?

edit: what are you gonna do if it turns out you cant avoid wayland? have you considered actually reporting the bugs you might see in wayland instead? because the future very much looks like A LOT of things are gonna go more and more wayland, its gonna be with reduced functionality to stay on X

Re: A Wayland Compositor in Minecraft

#87

Post by samtheDamned » Fri, May 29, 2026, 8:47 PM UTC

Philpax wrote: post #15

avaer wrote: post #14

Earlier quoted context omitted.

There are already VR overlay applications that do this on top of any game, not just Minecraft.

Yes, but part of the fun is doing it in Minecraft and using Minecraft's language for it (e.g. putting windows in your inventory, pulling them out of chests, etc)

Yeah the appeal to me would be the ability to have my desktop experience spread throughout an established home built in minecraft. I think in reality the added friction in a setup like that would be enormous but it's a pleasant thought.