That is BSD. You can go there. Cool people. Hardware support is a bit spottier though.
this post was submitted on 21 Apr 2025
798 points (98.4% liked)
linuxmemes
24607 readers
1686 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
This comic was posted in 2011 but still holds up today perfectly lol.
I think every thread ive seen the past 3 days has had an XKCD comic linked...
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.
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
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.
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).
For what it's worth, I regularly switch depending on what I'm doing (AwesomeWM for X11 and Hyprland for Wayland)
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
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.
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.
Multi-cursor support/multi focus
If I want two mice and monitors hooked up so me and another person can use the same computer independently itβs x11
Iβve seen some steps towards this on Wayland but it was in infancy last I checked
I think you can start two Wayland compositors, and change the compositor configuration to use different mice and outputs, but I never tried this.
Thanks for the tip
I'd wager that is true. I know, for sure, you can start one compositor inside another compositor. I do this all the time for gaming with gamescope.
load more comments
(4 replies)
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.
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.
load more comments
(2 replies)
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.
I still remember the old times before xorg.confs were modular. The truly hard times.
I remember when /bin/sh was the default shell, when you had to build grep from source. LILO was our bootloader. Dmesg was our seer. We made fire from a friction drill. Knapped our own blades from flint.
Simpler times.
... I don't remember building grep, nor do I remember a time before bash.
Are... Are you God?
I was there when the dark magic was written. In the time before git. The shell had not yet been born again.
The great wizard Stahlman still held sway in the high court, his Gknights of Gnu were just building their kernel. Lo gaze upon their mighty works and see they lie in ruin.
Torvalds was the true vanguard, he lead us to build the mighty kernel, to reverse engineer the binary blobs, coax the meaning from machine code, a thin line from serial to stdout.
No heirarchy but those inherited from the libraries. User space was our land, ~ was our home, #! was our flag. No gods, no masters, only code.
load more comments
(8 replies)
load more comments
(2 replies)
I was there, Gandalf, I was there when the modelines of xf86config failed...
Y'all have Desktop Environments?
Y'all are still using xorg?
I am definitely going to need my morning coffee. I see the word "Y'all" and I'm somehow thinking "shouldn't it be Xall if we're taking about X11? Wait what's wrong with my brain"
load more comments
(1 replies)
load more comments
(3 replies)
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).
"Story time" is just another word for "I'm showing my age"
It is a good way to know who's a Grey Beard
Well, in case my username wasn't clear enough lol
They ran rm -rf in their root directory.
French package goes brrrrrrr _
_
_ KERNEL PANIC
SEGFAULT 0x00000
EAX: _______
EIX: _______
I'm pretty sure it is because nobody knows. Xorg is a massive project that has tons and tons of duck tape.
professional tip for those who decided to rock Debian on a laptop with two GPUβs.
Envycontrol will take the headache away from manually configuring your xorg & xrandr, trust me, compared to the Debian documentation this will save you hours of your life.
load more comments
(15 replies)
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.
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.
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 Β―\_(γ)_/Β―
load more comments
(3 replies)
load more comments
(2 replies)
view more: next βΊ