• Im_old@lemmy.world
    19·
    7 days ago

    Gather around kids, story time. It was 2002 and I had a desktop pc with two video cards, one Matrox with dual video output (they were pretty much the only consumer ones with that at the time) on AGP slot, and one “something” (probably ATI, it still had and RCA port) on PCI. So I installed gentoo (from stage1, as it was custom at the time) and fiddled around with xorg.conf to have two monitors output from the Matrox and a third (yes, I had 3 monitors) from the ATI.

    That’s when I understood the power of Linux (no way win2000 was able to do that).

  • cley_faye@lemmy.world
    9·
    7 days ago

    I get the joke, but I’m getting tired of these very, very old memes being reposted ad-nauseam when they’re so outdated. I did not have to open the xorg.conf file for at least a decade, probably more. It was a very annoying thing to do, yes, but hasn’t been an issue for a lot of install in forever.

    There’s a resurgence of these “but it’s very weird/difficult/annoying” outdated memes these last few weeks on a lot of websites, and at this point I’m wondering if it’s just people discovering them or just some people bashing linux systems based on their experience from the last century.

    • superkret@feddit.org
      4·
      7 days ago

      It’s people entering the Linux space and wanting to join the tribe by posting Linux memes they found on google.

    • MonkderVierte@lemmy.ml
      4·
      7 days ago

      I did xorg.conf from the example on Arch wiki and it worked. Then i did it the correct way from the official documentation and it didn’t.

      • cley_faye@lemmy.world
        3·
        7 days ago

        I did not touch an xorg.conf file in forever and it just works out of the box, whether I’m running debian, kubuntu, or mint, so ¯\_(ツ)_/¯

          • cley_faye@lemmy.world
            2·
            7 days ago

            xrandr --rate 60. No need to mess with xorg.conf. And you put that on a start script to never have to type it again.

            • MonkderVierte@lemmy.ml
              2·
              6 days ago

              I have that on a key combo, together with --gamma for day/evening colors. But it is reset after display sleep. Funnily enough, even xorg.conf is ignored 50% of the times then.

    • Saleh@feddit.org
      41·
      7 days ago

      I broke xorg.conf when i installed Linux Mint about a year ago, but i forgot what for. Ironically i never had issues with an Arch based distro.

  • Abnorc@lemm.ee
    7·
    6 days ago

    That is BSD. You can go there. Cool people. Hardware support is a bit spottier though.

  • Downpour@programming.devEnglish
    261·
    7 days ago

    So I only just got into linux this year. I gave some X11 distro’s a go, but the screen tearing was awwwwfulll. So I’ve been running Wayalnd/Plasma for months now.

    What exactly am I missing out on? Seems lots of users here still favor X11 over wayland but as I’ve never had any problems. It’s still unclear to me why people are still sticking with X11.

    • superkret@feddit.org
      15·
      7 days ago

      If you have no issues with Wayland, keep using it. You aren’t missing anything.
      Linux is a vast space, and some people have use cases that aren’t covered by Wayland, yet.
      So they still use X.

    • Natanox@discuss.tchncs.deOPEnglish
      6·
      7 days ago

      Nothing, unless you really want to use a DE that’s still lacking behind in its adoption. There are a few tools that still only offer early support for it (like RustDesk), but otherwise Wayland is a way better choice these days. However if you got an Nvidia GPU and need to use the proprietary driver you might be forced to still use X11. Their pile of garbage still routinely bugs on Wayland, and given their work on NVK I doubt that thing will ever get fully fixed.

    • MonkderVierte@lemmy.ml
      4·
      7 days ago

      Xorg literally has a option to disable tearing: Option "TearFree" "true. If that doesn’t work and your compositor neither, fix your video drivers. Lookup Hardware Video Acceleration and similiar on Arch wiki.

    • SkyeStarfall@lemmy.blahaj.zone
      181·
      7 days ago

      Wayland is the new protocol and will be the one that everything uses in the long run

      If Wayland works for you, then that’s great, don’t use X11

      The main reason you’d want to use X11 these days is for compatibility. But that’s getting less and less of a concern as time goes on

    • brisk@aussie.zone
      16·
      7 days ago

      If you’re fine with Wayland, go with Wayland. There are lots of reasons still that people might prefer X11 but the list has been getting shorter.

      • The security model of Wayland is more restrictive than necessary for many users and means things like screen sharing and desktop toys are harder and not universally implemented or doable.
      • Wayland effectively requires many things to be handled by the same process, preventing traditional modular environments (e.g. separating window manager from compositor no longer possible)
      • Explicit compositor support required for more features, meaning having a feature complete environment in small projects is much harder, and the design of Wayland tends to promote a few large desktop environments rather than many small window managers.
      • NVidia’s support for Wayland is still improving
      • Wayland can’t rotate your screen to be on an angle to maximise the length of a line
      • Several programs I rely on don’t support Wayland well yet
        • Steam doesn’t stream from Wayland
        • Transparent bits of FreeCAD show the background instead of what’s behind them
        • Code-OSS required a very silly workaround for decent font rendering, although I think this might have been fixed in electron
      • desktop_user@lemmy.blahaj.zone
        3·
        6 days ago

        honestly my biggest complaint with Wayland is the lack of programs being able to move their windows causing browsers to not be able to properly display certain web experiences.

      • quid_pro_joe@infosec.pub
        5·
        6 days ago

        I’m new to Linux too and testing both X11 and Wayland at home. so far I like Wayland in theory (it’s the future!) but prefer X11 in practice (no weird graphical issues).

        • brisk@aussie.zone
          4·
          6 days ago

          For what it’s worth, I regularly switch depending on what I’m doing (AwesomeWM for X11 and Hyprland for Wayland)

    • cmhe@lemmy.world
      5·
      7 days ago

      I also switched to use different Wayland compositors many years ago for my main systems, but there are also still reasons to use X11. These are mine:

      • X11 forwarding, with that you can connect to another system via SSH (e.g. via ssh -Y) and just start a GUI app, and the window appears on your screen.
      • Sharing individual windows via WebRTC, with Wayland compositors you can normally only share full screens. Xserver allows applications to directly capture the window content of others.
      • Easily mirroring screens for presentations, with some Wayland compositors you have to capture one screen and then play it back on another screen, with X11 that is integrated into the xserver.
      • Automation and keyboard macros, with X11 it is much easier to automate keyboard macros and customize keyboard mapping than on Wayland. See Xmodmap, etc. Same for mouse input. That is also a reason why implementing remote control software is more difficult with Wayland, see for instance RustDesk support for Wayland (works now, but still a bit experimental).

      There might be some Wayland compositors that worked around that, but on X11 this was standard. But generally X11 provides these features for all WMs, and in Wayland they have to be implemented individually.

      And some just are not supposed to work, for security reasons.

      But all of this depends on your use-case. I sometimes even (can or have to) go without a Wayland compositor or X11 and render GUI directly via KMS/DRM.

    • SaharaMaleikuhm@feddit.org
      5·
      7 days ago

      They use it cause their desktop does not support wayland yet or their Nvidia card causes issue with it, potentially since they are using an older driver.

    • Possibly linux@lemmy.zipEnglish
      5·
      7 days ago

      I’m pretty sure it is because nobody knows. Xorg is a massive project that has tons and tons of duck tape.