BiggestBulb,
@BiggestBulb@kbin.social avatar

I think this is the perfect post to bring up XWayland.

That being said, I haven't used it yet (so I can't comment on whether it works flawlessly)! Can anyone elaborate on their experiences with it? I'm curious on it and don't have my hands on a Linux machine at the moment

Miyabi,
@Miyabi@iusearchlinux.fyi avatar

I have had a problem where some apps will just open to then show up as black. I can’t seem to figure out why its not working. It is what it is.

mactan,

not flawless but barely noticeable that it’s there. only time I’ve ever had issues was with cursor warping in one game

BiggestBulb,
@BiggestBulb@kbin.social avatar

Interesting, thank you for sharing. I'll have to give it a go next time!

Thordros,
@Thordros@hexbear.net avatar

I don’t know anything about Linux, but I believe they merged with the Yutani Corporation in 2099.

halm,
@halm@leminal.space avatar

Justice for the colonists of LV-426! ✊

CarbonScored,
@CarbonScored@hexbear.net avatar

Wayland is the fancy new standard that never seems to stably work for me on any of my machines :( Thanks for letting me revert to X in the login screen, GNOME.

nobloat,

Great answers here. I’d just like to add that X and Wayland are not completing. In fact, most of the Xorg devs are the ones working on Wayland. You can find Wayland mentioned in the Xorg Foundation Website.

wiki_me,

On top of what other said, the wayland project also maintains the wayland protocols repository which includes additional protocols that are approved by a “committee” that includes representatives from wayland protocol implementations (wlroots, kde , gnome , smithay etc). for example now they are working on color management.

There appears to be a consensus among people working on window manager implementations that X has to go and wayland is the future.

Wayland has technical benefits, if you want the nitty gritty details see this.

Basically X11 is bad IPC at this point.

Also be careful with what you read online, I see misinformation about it relatively often.

Moobythegoldensock,

You’ve already gotten great answers on what Wayland is, but as far as who should care:

Mainly developers and users with niche workflows. People with NVIDIA cards should care a little as initially NVIDIA did not support Wayland, but NVIDIA drivers are catching up so this should continue to improve. Most users should just switch when their DE switches.

Cysioland,
@Cysioland@lemmygrad.ml avatar

Yes, X is actually going to die.

InstallGentoo,

In two more weeks

take6056,

Explained by someone that doesn’t know the technical side super well.

1: It’s a new protocol for displaying. The main difference from X11, as I understand it, is a simplification of the stack. Eliminating the need for a display server, or merging the display server and compositor.

2: Some things impossible (or difficult) with X11 are much better supported in Wayland. Their not necessarily available, as the Wayland protocol is quite generic and needs additional protocols for further negotiation. Examples are fractional scaling & multiple displays with differing refresh rates.

Security is also improved. X11 did not make some security considerations (as it is quite old, maybe justifiably so). In X11 it’s possible for any application to “look” at the entire display. In Wayland they receive a specific section that they can draw into and use. (This has the side-effect of complicating stuff like redshifting the screen at night, but in my experience that has fully caught up).

3: If you’re interested, are in desktop application development (but I have no experience in that regard) or have a specific need for Wayland.

4: I think X won’t die for a long long time if “ever”. I’m not super familiar with desktop app development, but I don’t think it requires more work to keep supporting X.

On the other hand, most of the complaints about Wayland I’ve heard were ultimately about support. At some point, when you’re a normal user, the distro maintainer should be able to decide to move to Wayland without you noticing, apart from the blurriness being gone with fractional scaling.

Vorter, (edited )

I’m not super familiar with desktop app development, but I don’t think it requires more work to keep supporting X.

It doesn’t depend that much on desktop application developers, but on GUI toolkit developers. It does need more work for GTK and Qt devs to support both. But the outcome will likely depend not that much on ammount of work as on “political” decisions. RedHat are now somewhat actively forcing Wayland in their distros. They also have their impact on GNOME, so it’s not impossible that due RedHat’s decision GNOME and then GTK (that is now developed mostly by GNOME developers, despite being GIMP Toolkit initially) will ditch X “just because”.

End user Application developers usually don’t deal much with Wayland or X — they just use toolkits (GTK or Qt for the majority), and toolkits do all the under the hoof work for them.

Vorter,

In short, Wayland is a protocol for graphics.

It’s somewhat similar to X, as its main purpose is the same, however the archivecture is very different, and Wayland is much simpler/barebone.

If X is going to die or not — only time will tell. For now it can be considered another competing standard.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • localhost
  • All magazines
  • 200 @ entry_single
    HTTP status 200 OK
    Route name entry_single
    Has session yes
    Stateless Check no
    Time 768 ms
    Total time 768 ms
    Initialization time 46 ms
    Memory 20.0 MiB
    Peak memory usage 20.0 MiB
    PHP memory limit 128 MiB
    Cache 1
    Number of forms 1
    Number of errors 0
    Logger 89
    Errors 0
    Warnings 0
    Deprecations 89
    Cache 120 in 417.43 ms
    Cache Calls 120
    Total time 417.43 ms
    Cache hits 69 / 117 (58.97%)
    Cache writes 38
    641
    Default locale en
    Missing messages 641
    Fallback messages 0
    Defined messages 152
    Security n/a
    Authenticated No
    Firewall name main
    Twig 577 ms
    Render Time 577 ms
    Template Calls 244
    Block Calls 82
    Macro Calls 6
    180 in 506 ms
    user_avatar 27
    date 21
    user_inline 17
    date_edited 16
    vote 16
    boost 16
    entry_comment 15
    entry_comments_nested 15
    settings_row_switch 15
    user_settings_row_switch 4
    magazine_inline 3
    settings_row_enum 2
    entry 1
    entries_cross 1
    editor_toolbar 1
    user_actions 1
    magazine_box 1
    magazine_sub 1
    related_magazines 1
    active_users 1
    related_categories 1
    related_posts 1
    related_entries 1
    support_us_block 1
    featured_magazines 1
    33 in 329.83 ms
    Database Queries 33
    Different statements 19
    Query time 329.83 ms
    Invalid entities 0
    Cache hits 39
    Cache misses 7
    Cache puts 7
    6.4.0
    Profiler token 9cb984
    Environment dev
    Debug enabled
    PHP version 8.2.26   View phpinfo()
    PHP Extensions Xdebug ✗ APCu ✓ OPcache ✓
    PHP SAPI apache2handler