Mozilla Firefox 116 Now Available - Capable Of Wayland-Only Builds

[mrg666]

If there are so many X11 loyalists and need for using it, the code would have been forked and development continued already. The code is there and will stay there, and if there is any real need, it will forked. The people throwing tantrums here are just whiners, incapable of contributing anything.

[Monsterovich]

Wayland is x12

Bullshit.

Wayland is not an evolution of X11. They are different things that are built on different principles.

[mrg666]

Bullshit.

Wayland is not an evolution of X11. They are different things that are built on different principles.

So you know so much about X12, I guess you are one of the developers. Now that you have revealed it, Is it too much to ask when is the release date? I just can't wait

[cl333r]

So you know so much about X12, I guess you are one of the developers. Now that you have revealed it, Is it too much to ask when is the release date? I just can't wait

Why argue in favor or against a dead project (?), especially since by now it's clear that Wayland is the only way forward.

[oiaohm]

Wayland is not an evolution of X11. They are different things that are built on different principles.

This is absolutely not true that Wayland and X12 are completely different set of principles. Wayland is built from subset of X12 design principles like it or not.

From the "A Rough List of Requirements" in X12 shock horror wayland was designed to allow all of them. Yes Network transplant the start of waypipe was demoed by the core Wayland protocol developer.

Wayland is what happens when you take X12 and make a protocol from the ground up based off the Rough list of Requirements of X12. That rough list does not have independent windows manager to protocol and does not say remote desktop network code has to be built into the core protocol just be possible..

A12 as in Arcan-fe protocol is also written based on X12 document but even the Arcan-fe developer found sections of the X12 document not implementable in any sane way .

Monsterovich its really simple to forgot the core Wayland developers were core X11 developers and they were in the group who wrote the X12 wiki page at x.org this is why you are wrong to say completely different principles because large percentage of the principles in the X12 wiki page were in fact put there by the developers who created Wayland. The growing list of parts of X11 that need fixing being documented on the X12 page is one of the reasons why Wayland was attempted as a rebuild from the ground up.
.
Monsterovich this is the catch two different groups have looked at the X12 document and attempted to implement it as written that be the Wayland group of developers and the arcan-fe developer both found the X12 document flawed and implemented subsets of the X12 document.

There is a possibility that Ubuntu Mir developers are a third group to take the X12 document and go this cannot be implemented as well.

The reality like it or not X11 core design does not suit modern day GPU hardware and once you start working with goal to exploit modern day GPU hardware lots of areas of X12 document don't work leading to arcan-fe and Wayland both being subsets of X12 design principles. Yes Wayland is the smallest subset of X12.

Please note X12 design document does not say X12 has to be a direct evolution of X11. Also not true that Wayland is completely different set of principles to x11 thinking the core Wayland developers worked on X11 for over decade before writing Wayland core there is a lot of X11 design principles still in Wayland because you write what you know.

[Monsterovich]

wayland_fan_bingo.jpg
oiaohm Awesome, I won the Wayland fan bingo!

[MrCooper]

Audacity is the only app I use and know of that needs X11. May X11 RIP soon.

It can run Wayland native here. If it doesn't by default for you, you can try

GDK_BACKEND=wayland audacity

[Monsterovich]

So you know so much about X12, I guess you are one of the developers. Now that you have revealed it, Is it too much to ask when is the release date? I just can't wait

The point of X12 is to update the protocol and make it fully backward compatible with X11 (via layers for compatibility). In general, it will be the same graphical server with all the libraries, just another reworked version of the protocol where the limitations are removed. Right now it doesn't make sense yet because X11 is still relevant.

Wayland is just a spec that has no libraries or server, so each DE is a separate incompatible graphical server which should implement even basic desktop features from scratch. The rest of the features that don't fit into Wayland's crappy architecture are done through crutches like Pipewire + D-Bus (mandatory!).

The fragmentation also exists for all other desktop features: color management, shortcuts, window management, etc.

This is just the tip of the iceberg. How can this all be considered X12 and a successor to Xorg?

[elatllat]

It can run Wayland native here. If it doesn't by default for you, you can try

GDK_BACKEND=wayland audacity

https://github.com/audacity/audacity/issues/4821

[Myownfriend]

Bullshit.

Wayland is not an evolution of X11. They are different things that are built on different principles.

Nobody said it's an evolution of X11. It's it's successor.

You said X12 is X11's successor yet you chose not to respond to my post showing how X12 would have been similar to Wayland? Why is that? Are you a coward?