this post was submitted on 12 Jan 2024
296 points (81.2% liked)

linuxmemes

21220 readers
111 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 5 points 10 months ago

    if developers keep pushing incomplete and buggy software to the end users instead of actually fixing bugs

    My understanding is, the issue is that fixing bugs in X has become too much of an issue due to bloat and bad historical architecture, so the developers working on it - and providing the software for free, if not working for free - instead worked together to develop a new standard aiming to fix the issues inherent to X's code and design.

    The "list of problems" is absolute bullshit right from the start. The first two sections are "It didn't used to work like this in X, Wayland is trash!" and "I had some screen recording software using X APIs and they don't work when not running in X!". In fact, a lot of them follow this pattern, blaming Wayland because it doesn't have 100% backwards compatibility. It's not an X rewrite, it's meant to be a new, better piece of software.

    I will not deny that Wayland has problems, of course - but those mostly come down to NVidia refusing to support open protocols, missing features that are yet to be implemented, and missing software support for Wayland.

    I will also say that on Arch, which doesn't assume I'm using X, Wayland does work completely fine for me when following instructions. It might be an issue with the distro you're using not having good support, or one of those edge cases like problematic hardware. I definitely agree that you should stick with X for now if you have problems, but I'll also say that you're getting it for free, and if you don't report problems, they might also not know about them, for example because it only occurs on specific hardware.