Interesting. Reminds me of what they were trying to do with MicroXWin, Y, DFB, Xynth and Fresco!

At a certain point if the restaurant or building developer (rarer and harder but still i think government would also apply with scope) isn't filling all my wants or needs, yes you do start your own with all of those things (or someone in the community does to fill the want/need if they recognize it)

A great deal of the things we use were at one time someone or some group wanting something the status quo wasn't providing.

And how do you begin to figure that out?

By openly talking about it with your community, which includes people who may not be the builders.

The pro-Wayland folks appear to believe that this -- talking about and being critical of software that a lot of people may use -- is a bad thing.

As I like to say, suck it up, use Wayland, file bug reports.

Criticizing Wayland is great if you do it with the intent of improving Wayland.

Encouraging people to fuck off back to X is counterproductive because X is a DEAD END. It's like Republican politics: all it does is obstruct useful progress, by design. The maintainers of Xorg have decided that Wayland is the way to go, as have the maintainers of the major toolkits, DEs, and distros. Spreading FUD about Wayland in an attempt to encourage people to stick with X generates more heat than light, and is ultimately useless because no one wants to maintain X or the X code paths; these will eventually break or go away. Wayland is the community-supported option going forward. You can't even count on kernel support for X: the Asahi Linux kernel display driver actively detects if it's being called from an X server, and fails if it is.

When it comes to alternatives to both X and Wayland... good luck attracting the developer expertise and mindshare that Wayland already has. It's like coming up with an alternative to Facebook.

Ha!

I teach college students; they mostly don't use Facebook because there are already literally lots of alternatives, and they didn't come about because of gatekeeping the commentary about the tech. Perfectly wrong example you gave there.

There is some credence to the "make your own or shut up" argument here on HN.

If we reconsider your "criticize a restaurant" analogy, we are not random folks walking into a restaurant. We are professional chefs criticizing the output of other professional chefs.

In that context, "go start your own restaurant" does actually make sense.

Not every chef has the means (e.g. money and time) and/or non-food experience to start a restaurant. Constructive criticisms, and not all criticism is constructive, should always be taken in earnest; that said, there is also a matter of taste: just because one chef puts in extra garlic and another doesn't like that doesn't mean either is "wrong" or "right".

Lol, that's exactly how you get e.g. "Stupid food/we want plates" on reddit.

One of the worst things in computing is this sort of gatekeeping; it's not only "professional chefs" here, it's people who want to democratize more of software building, not reintroduce more silos.

Indeed, and when one doesn't like it, can eat at home, run for elections, do a building injunction, and so on.

Or accept what exists and that is it.

Or, you know, just talk about it and openly criticize.

I'm going to go with e.g. the framers of the Constitution and others who actually think this is a good thing.

The framers of the Constitution have put lots of work, suffering, blood and lost lives to make it happen in first place, they didn't just talk about it in newspapers and saloon tables.

And they did so to ensure that only people who did that had free speech, or so that everyone could? Come on now, be smarter.

They did it to free the slaves and unite the country.

If it were for anti-Wayland people mindset, nothing would have changed, they would only complain about it on newspaper readers section.