PHJF wrote on May 28, 2021, 08:38:
Burrito of Peace wrote on May 27, 2021, 22:25:
PHJF wrote on May 27, 2021, 15:11:
Yeah because installing drivers via a command line is a lot easier than clicking a .exe? I had a *massive* two-hour headache trying to install a wifi dongle driver onto an unconnected Linux box.
Broadcom?
Yeah, it was. Every "guide" for installing device drivers basically says "just open a terminal and type in sudo package install www.package.com/driver" or some such... which is kind of fucking hard to do when the device you are trying to install is a network adapter.
Knew it. Broadcom chipsets suck even on Windows and their drivers are only slightly better than Qualcomm's Atheros garbage.
That's a fair point, however. I will say that, today, most mainline distros (Not you, Fedora. Sit down.) provide the drivers for a lot of mainstream hardware out of the box. Ubuntu, Mint, and Manjaro spring to mind with the "broadcom-wl" or "b43" packages. There might be some chipsets that fall outside the scope of support for those packages but they, the chipsets, would be fairly esoteric.
The flip side is that randomly clicking executables holds an inherent security risk whereas a properly maintained official repo acts as a better curated and more secure download location. On top of that, with a package, I can choose not to install garbage apps that are bundled in to executables like "helper" apps. Just give me the firmware and drivers, thanks. I don't need whatever app some developer paid a third world code monkey five bucks to build shitting in my tray.
"Just take a look around you, what do you see? Pain, suffering, and misery." -Black Sabbath, Killing Yourself to Live.
“Man was born free, and he is everywhere in chains” -Jean-Jacques Rousseau