2024: The Year Linux Dethrones Windows on the Desktop – Are You Ready?
2024: The Year Linux Dethrones Windows on the Desktop – Are You Ready?
- NTSync coming in Kernel 6.11 for better Wine/Proton game performance and porting.
- Wine-Wayland last 4/5 parts left to be merged before end of 2024
- Wayland HDR/Game color protocol will be finished before end of 2024
- Nvidia 555/560 will be out for a perfect no stutter Nvidia performance
- KDE/Gnome reaching stability and usability with NO FKN ADS
- VR being usable
- More Wine development and more Games being ported
- Better LibreOffice/Word compatibility
- Windows 10 coming to EOL
- Improved Linux simplicity and support
- Web-native apps (Including Msft Office and Adobe)
- .Net cross platform (in VSCode or Jetbrains Rider)
What else am I missing?
You're viewing part of a thread.
If minor issues like this bother you while major issues like data collection and ad pushing dont
As I pointed out, I'm using it because MS is screwing the pooch with those issues.
you dont want to participate in making linux better by submitting bug reports
These are known issues, and have been around for more than a decade. They're not bugs, they're missing basic features. But sure, go ahead and assume stuff.
Its very much like owning a house or a ranch. You‘re free of others and can do whatever you like. But you do have to do your own maintenance.
If you want to go back paying rent for a shoebox apartment, thats your choice.
It's probably closer to renting a apartment vs owning a shack (or it was, before said screwing of said pooch). You can upgrade it into a mansion if you want, but that's not where you start.
As I pointed out, I'm using it because MS is screwing the pooch with those issues.
Fair enough
These are known issues, and have been around for more than a decade. They're not bugs, they're missing basic features.
Then make a fork and or PR. i‘m only around two years and I make the stuff I need.
But sure, go ahead and assume stuff.
As a human does since your small text can never have full information needed to know everything. For the sake of discussing things I have to either ask and widen the scope of the discussion or I assume where it seems appropriate and you correct me if I‘m wrong. Sorry if that is new to you.
It's probably closer to renting a apartment vs owning a shack (or it was, before said screwing of said pooch). You can upgrade it into a mansion if you want, but that's not where you start.
If thats your opinion I‘d like to own a „shack“ because in germany, where I live, the houses even need maintenance and repairs if you buy them.
A more classic example of linux users pushing others away, I could not have come up with.
"I have so-and-so issue"
"Fork the OS and fix it yourself!"
Yeah, no. I already spend 8 hours a day programming, I'd like my free time to be spent elsewhere, thanks.
I‘m a tech myself and I know this discussion from 100 times this has occured.
- someone complaining about something openly instead of using the proper channels
- someone suggesting they use the proper channels
- they denying that its an issue they can help fix but a general failing of the software/vendor (typical proprietary software-user behavior)
- person trying to help pointing out that this is not helpful behavior
- person complaining getting defensive and falling for a logical fallacy instead of seeing their mistake.
But yeah, good luck mate.
- someone complaining about something openly instead of using the proper channels
I refer you back to my original statement. I was not asking how to do something. I was grousing that basic tasks are extremely user-unfriendly to configure. I've fixed it on my computer. That's not the topic under discussion.
- someone suggesting they use the proper channels
What proper channels? We're in a post claiming it's the YOTLD again, because OP apparently doesn't realise it's been claimed every year for the last couple decades. I'm posting about why that's not gonna happen this year either.
- they denying that its an issue they can help fix but a general failing of the software/vendor (typical proprietary software-user behavior)
I could fix it. However, I have no intention of opening a PR and spending what little free time I have contributing to open source (I'll contribute money, but not my time). Kudos to those who do write and maintain open source, but that's not for me.
- & 5.
I think you can see how we've diverged into entirely different directions already.
I can see your point and appreciate you elaborating.
You do see that you went there, right?
"I have so-and-so issue" "Fork the OS and fix it yourself!"
Because, please don't make that recommendation to anybody else. Of all the places for somebody to start contributing to open source, linux is probably among the top in complexity. And if it's a new user, as per the original topic of this post, and they can't figure out their issue from the million guides online, you're just ensuring they make a speedy return to windows.
Sad, we were almost aligning here. Now we will just have to disagree here.
I will make this exact recommendation to everyone in every situation because the end user mentality is making us speedrun our planet to shit. People need to take responsibility for their own stuff instead of letting corporations control them. This obviously means they need to relearn that an error is not a sign of bad code/software but something that can happen. The perfectionism this world is succumbing to is a cancer that will kill us all.
But good luck anyway.
You're suggesting that every user should learn programming. All 8 billion people. How do you not see the ridiculousness of that suggestion.
Hahaha. Yeah, exactly. Right after I suggested everyone work at mcdonalds. Whatever it is you’re taking, its either too much or not enough.
The "make a fork" thing is part of the issue, I think. In general there's this culture in the open source community that if you want a feature, you should implement it yourself and not expect the maintainers to implement it for you. And that's good advice to some extent, it's great to encourage more people to volunteer and it's great to discourage entitlement.
But on the other hand, this is toxic because not everyone can contribute. Telling non-technical users to "make it yourself" is essentially telling them to fuck off. To use the house metaphor, people don't usually need to design and renovate their houses on their own, because that's not their skillset, and it's unreasonable to expect that anyone who wants a house should become an architect.
Even among technical users, there are reasons they can't contribute. Not everyone has time to contribute to FOSS, and that's especially notable for non-programmers who would have to get comfortable with writing code and contributing in the first place.
I appreciate you elaborating on this. Let me try and explain this:
Imo you’re on point with the house metaphor. People dont have the skills to redesign and repair their house.
Thats why they pay people to do it. They get a carpenter to fix their floor, a painter to fresh up the outside walls, an electrician to fix that damn outlet thats acting up. Some house owners have to forgo vacations because they need repairs done this season. They also spread out repairs and live with a broken thing in between.
And the same works for software. I dont mind fixing something in your software, as long as you pay me. Part of the problem is that companies made people believe that everything can be perfect and free. Its like Odysseus going insane by the song of the mermaids. Its a trap. Real software isnt perfect.
Next point is people cant controbute:
People can always contribute. Not everyone can code but they can press the report button and try to be concise in describing the problem, they can help translating, they can help packaging if they know their way around files and much more. The issue is that its uncomfortable to do something while we are used to getting paid for most things and also are used to get perfect proprietary software.
Again, thanks for answering and have a good one.