this post was submitted on 27 Jun 2026
97 points (98.0% liked)
Technology
85804 readers
3668 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I gave Linux another try lately and went back to Wondows. I already had Fedora all my secondary laptops, but wanted it to be my primary personal+work system.
I purchased a brand new built computer. AMD 9950X AMD Creator B870X with 10Gbe PNY 5080 16GB 128GB DDR5 6400 cls 30
After installing Fedora, almost immediately my wifi wouldn't work. And both my 1Gbe and 10Gbe would work and randomly disconnect. I was finally able to fix it with drivers that I built and fixes in bootup.
I spent a good week working on this including getting used to a alternative Adobe apps and figuring out how to use Bottles for some of my crucial work app.
While in the middle of me coding for work, the computer experienced a panic. But not a regular panic. Because no matter what I do, the panic wouldn't record a log. I went as far as building an app to try and capture the panic. No go.
Before you tell me to use Ubuntu or whatever. This problem isn't a Wayland problem. This happened in Ubuntu as well.
The amount of time spent and work lost and client zoom calls that crash makes it impossible to have Fedora/Linux as a work system. I gave up. Went back to Windows. I'm still using WSL. It's just that Windows is simply more stable at the moment.
I did install Winhance which eliminated the over-reaching Microsoft problem.
That sucks, sorry to hear that
Thanks man. Windows get a bad rap and I bitch about it all the time, esp with what they are doing now with their copilot and shit. But at the end of the day, their shit works. Poorly, but works. And in my line of work, stability is the key metric.
If you had started on Linux, you'd have stability due to familiarity.
Moving to something unfamiliar is HARD. Since I'm the nerd in the friend group, I'm sometimes tasked to address issues.
Helping someone with a Windows 11 issue was hard, because all of the familiar tools I used in Windows 7 (the last version I spent a bunch of time on) had been moved or looked completely different. I was lost for a bit. I knew what the problem was, but I couldn't figure out how to get to the tool to troubleshoot and fix.
If you decide to try again, take it slow, and figure out how to fix issues as they arise. Once you become familiar, things get easier, I promise.
Maybe you're right. My main GUI has always been Windows and I'm used to having apps that is more mainstream.
But maybe it's not just that I'm not familiar with Fedora.
I am a developer with Linux racks at home. So I'm not unfamiliar with Linux. I'm quite familiar with CLI.
I think the main point I'm making is that my system was crashing too much due to poor HW drivers. Even tho it's really not the fault of Linux, it's just too buggy to be running in production. At least the GUI isn't ready. My Linux servers had been bulletproof.
I can assure you my UI is stable. But only because I'm familiar with how to make it that way. Sometimes I break things because I like to learn how to fix them (I did that on Windows too).
I agree with you, Linux servers are amazing. I have a NUC here running a bunch of services. I use Gentoo because it gives me a ton of flexibility to wander into unusual territories easily.
Best to you!
As to you too!!!
If only nVidia would do what AMD did and have open source kernel drivers, but no, the drivers you need are in a closed source package... same for shame Intel closing their drivers too... it's like we're back in the fwcutter days again.
Surprising enough the video drivers was pretty painless. So many people before me already solved the issues. I was able to get 240fps on my monitor when previous attempts have failed.
The main issue was the motherboard. It's too "new" and I ended up having to build a bunch of drivers to just get my computer to work exactly what Windows provided out the box.
There is so much hate for Windows, but you can't beat their commitment to stability and backwards compatibility.
Linux has an uphill battle. With how poorly Wayland is performing and the x11 crew not embracing it and how stable Apple and Windows OS is. Linux is not ready. This is coming from a developer POV.
Ok.. To be fair, the drivers for Windows are probably all third party drivers. HW companies tend not to provide standalone drivers for Linux - either they contribute specs and/or patches that get incorporated to mainline, or do squat and eventually someone will reverse engineer it and create a driver.
This isn't the problem you just described, ftr. Linux often has a delay in supporting the newest hardware, but then supports it well and for a long time. OSS in general is good at that.
For example: my Wacom tablet is no longer officially supported on Windows (by Wacom), while it works out of the box on Linux.
Another example: Windows 11 refuses older hardware - not backwards compatible.
If you are talking about software APIs, that's a different story. eg. There's not much point in targeting Linux native APIs for games, because wine usually works better.
Yes for sure I had too new of a system and nobody has figured out the bugs yet. Most of this fault is from the hardware corps.
I think for a high performance late model Linux, this is too bleeding edge for Linux. Without HW support, new hardware simply isn't ready for production.
Maybe I'll wait a year or so and try again. Hopefully they work out the kinks.