Hacker News new | past | comments | ask | show | jobs | submit login

As TFA says, people _are being forced_ to adopt Wayland. You yourself are saying that "you outsource your concerns to the distro maintainers, and some are choosing Wayland", which effectively implies that you are being forced to use Wayland.

I am also forced to support Wayland if I want to make Linux desktop software. Which means (again) the next application or game I would make is likely going to target Win32 only instead of Linux since it changes way too damn frequently for no reason. The argument "if you complain about Wayland, just improve X11!" goes both ways. The "shiny new thing" chasers are forcing me extra work to maintain my own software, and I am also not paid to do it.




Nobody is forced. Just like with systemd, there's plenty of distros that still don't use it if that's your thing. Today, they're mostly niche distros for people that just cannot adapt...

You can choose not to support Wayland in your app if you want. As market-share grows, your available reach will shrink. That's the same as with anything...

There's good reasons Wayland is being adopted in major distros - and it's not "the shiny" like you asserted.

> the next application or game I would make is likely going to target Win32 only instead of Linux since it changes way too damn frequently for no reason

That's ridiculous. We're talking about one major change in 20 years and you're acting like it changes every few months. Your game won't even exist in 20 years, so it doesn't matter. Nor do you have to even care about what protocol/compositor/lib is being used unless you're doing something strange - the engine will take care of that for you and probably make it a checkbox.


> Nobody is forced. [...] You can choose not to support Wayland in your app if you want. As market-share grows, your available reach will shrink.

What is the point of claiming "no one is forcing you to choose X" while at the same claiming "but if you choose Y you will face the consequences"? In this case the consequence is a million frustrated users not being able to say, take a screenshot, spamming my inbox like crazy, me abandoning Linux desktop development and everyone getting frustrated at the state of the Linux desktop yet again.

> There's good reasons Wayland is being adopted in major distros - and it's not "the shiny" like you asserted.

Even in your own messages you are throwing the argument that "at least Wayland is maintained and Xorg isn't", which is basically another way of saying that it has developer interest, and my claim is that it has developer interest because it's new.

> Your game won't even exist in 20 years

The software I am talking about is actually already older than that.

> Nor do you have to even care about what protocol/compositor/lib is being used unless you're doing something strange

As mentioned in TFA, there are several extremely common usecases which are broken by these changes. Certainly Wayland is just part of the problem, as it is pervasive to this world.


If you're software is older than 20 years, then you had to deal with this same issue ~20 years ago.

ie. it's a non-issue... do the work and update or don't. That's your choice.

Wayland is only slightly newer than X.org - and it's been on the horizon for years and years already. If you haven't updated by now, then you made that choice.

The folks maintaining X.org know there are issues that cannot be overcome without a major re-write and protocol change. The change has to happen even if it was a X.org v2... and you would still be complaining.


also the x12 protocol has the same wayland concept on mind, so wayland is x12, and xorg developers are the one working on wayland, who is better to know how hard is to maintaing the software than the same mainteiners?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: