381
I don't...
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Jan 2024
381 points (100.0% liked)
linuxmemes
21355 readers
1404 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 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
sudoin 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!
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 fork-bomb your computer.
founded 1 year ago
MODERATORS
Wayland is still too immature. I couldn't get it to work on my Kubuntu distro.
And then there's this list of problems with Wayland.
https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277
BEGIN RANT
"Move fast and break things" may be fine for software gurus who love to experiment and have no problem hitting their head against the wall every few days while believing in the promise of a free-to-fix future, but this isn't true for poor or busy people who are NOT middle class folks living in their own house in a suburb with a garage full of computer parts. There are single parents, caregivers with disabled and/or elderly, folks who need a reliable computer for their studies, and in general people who simply need something that JUST WORKS.
I'm a caregiver, and unfortunate I'm poor enough that I don't have money to buy a commercial OS. Heck, I wish Windows just worked instead of making old versions obsolete. I was perfectly fine with Windows 7 ten years ago until Microsoft started doing planned obsolescence bullshit with their forced updates. I had to switch to Linux because Windows became very unreliable and I needed a stable platform that wouldn't ruin my work.
(So if you're one of the persons who reply to "Help my Linux is having problems" with "well you should know Linux is like that, you should have thought it twice before switching", then you're part of the problem because that's a very, very shitty answer to give to a non technical end user with limited time and resources)
The year of the Linux desktop will never arrive if developers keep pushing incomplete and buggy software to the end users instead of actually fixing bugs and delivering their stuff ONLY when they're ready.
Wayland is NOT ready for the end user.
END RANT.
Bro, wayland is 15 years old
CC BY-NC-SA 4.0
If it's still so buggy then that's even worse!
And please don't call me bro.
More than enough time to make something that is not as shitty as it still is.
Go on then. Make it better, or make a better one.
CC BY-NC-SA 4.0
Ah yes, end users have no right to point out a software's flaws unless they're better than the developers who made it.
Don't tell me you forgot what a "non technical end user" is?
Users can't even add a feature request because they're met with a storm of insults and snobbery.
Well, I have some news for you: You can't hope for the year of the Linux desktop and keep treating end users like shit.
Pointing out flaws is fine. Shitting on devs, is not, just like devs shitting on users isn't.
Don't be surprised if you attack somebody and they defend themselves.
Saying "X doesn't work" is completely fine. Writing a rant about how opensource devs don't think about people, yadayada. Buddy, these are people giving up their free time to write stuff. Nobody's forcing you to use it. There are no guarantees provided, no warranties either. It's provided as is.
The way you are is as if someone built a free house in the woods, you showed up and complained about how the door is creaky, the toilet leaky, a draft coming through the windows, and you wrote a review online disparaging the free work. Does that sound like good behavior to you?
How did you write the feature request? "I demand this be implemented because you're providing a product and I'm a customer" or "It would be great if X were added for reason Y"? If it's the latter and you were met with unkindness, of course that's shit, no doubt.
CC BY-NC-SA 4.0
I understand devs being busy. What I can't stand is their fan club who keep shitting on every user asking questions or not having the time to do a deep search on every single solution and the problems that come with it.
Maybe this is news for you, but FOSS communities are incredibly toxic. Every single suggestion or legitimate complaint is taken as a personal attack.
Then they wonder why people don't pay enough attention to Linux and Open Source Software in general.
Perhaps they should realize there's too many assholes in the community who keep driving people away. Normal folks have a limit. They just leave and hope their Windows doesn't crash away, which is less frustrating than having to personally deal not only with tech issues but the shitty attitude of peple who are knowledgeable enough.
Worse, when you want to point out a flaw, you need to build an exhaustive list of reddit posts, archive org pages and so on and face trial because unless you give every single piece of evidence then your complaint is invalid. And I'm sorry but normal people just don't have time for this shit.
Remember that joke? Ask for help and you get no response; Say linux sucks because you can't do X and you get dozens of apologetic posts explaining step by step how to do stuff.
Turns out there's some truth behind that joke.
So there are two points:
Still point 2 does not invalidate point 1.
I've had to deal with toxic ubuntu, debian, arch, nixos, rust, java, python, ... communities. The ones that piss me off the most are linux communities that treat newcomers like gutter-filth, refuse to endorse GUIs, good documentation, and just a generally better newcomer experience, then wonder why there's no "year of the linux desktop". I hate those gatekeepers with a passion. "If you use Linux, you must learn to use the command line", no how about you fuck off to whatever CLI cave you came from and learn to be a productive member of the community?
As I said, I get it. But again, writing an angry bug report, demanding a new feature be implemented, writing a tirade about "how bad opensource software is" or whatever? Nah. Not OK
Sad but true.
CC BY-NC-SA 4.0
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.
You're not wrong but also misinterpreting this. Yes, it's bad to push incomplete software on end users, and it's even apart of the entire development ideals of Linux: never break userspace. There's even small bits of code (see: egrep and fgrep) in the core commands that has been on the chopping block for removal for 2 decades but hasn't because removing them would break apps.
The choice of PUSHING Wayland on end users is not up to the developers making wayland, it's up to the distro maintainers, and this image honestly doesn't even make sense. Most distros right now are either so nothing, and the ones that do are disabling Wayland until it's more feature complete. The only big distro I remember that's specifically is pushing for it is Fedora, and Fedora is specifically known for pushing for new initiatives.
X11 works just fine, and will work just fine for a long time, and if there's ever a point where a majority of apps start dropping X11 support for Wayland, it's going to be because Wayland just works by that point and has for long enough for devs to care.
That article itself against has been a pain point for years because it over-dramaticises a lot of the pain points about Wayland and a lot of the issues it touts don't... exist anymore. I've used lots of software like OBS on Wayland just fine a long time ago even though the article says it's been broken for years. Nvidia on Wayland has also just gotten to a good state on proprietary drivers while the article implies you need the crappy open source drivers to use Wayland at all, which hasn't been true for a very long time. I could go on about this article, but Brodie Robertson has already talked it to death on YouTube.
Wayland does "just work" (no bugs, no configuration, just switch to it and nothing breaks) for a lot of users at this point, and I'm tired of this article ignoring that and trying to make it seem like Wayland is this buggy slop everyone's being forcefed when it's not.
This is also one of the many reasons why Linux as an OS fails to establish a bigger user base. Of course, this is one of the smallest problems, but it still is.
Like Linus said, every tool every dev made was usually because they wanted to fix problems in their workflow, not because users needed something that they can provide. Sure, I'd also look at things from this perspective. After all, god made his beard first, not everyone else's, but the trouble is, things don't really move fast enough in that direction. Don't get me wrong, there has been progress in GUI tools, but not enough IMO. Most tools are terminal based, and while that is not a problem for most UNIX type OS enjoyers, that is a problem for your averige Joe. That might not be the crowd we're trying to get off of MS and Apple products, but they still play an important role IMO, more of a guide as how a UI should look and feel to the average user. Linux and other UNIX based OSes kinda messed up with this one. Things are getting better though, have to say. I don't use some of the UIs for stuff people usually do, but I have tried a few and I have to say that things are moving in the right direction the past few years. Just not fast enough...