this post was submitted on 18 Dec 2024
358 points (99.7% liked)

Linux

8305 readers
122 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] stiephelando@discuss.tchncs.de 22 points 4 days ago (1 children)

Wtf, I use Linux and have never compiled anything.

[–] FoolHen@lemmy.world -1 points 4 days ago* (last edited 4 days ago) (2 children)

That doesn't mean that others don't have to. I installed Debian on a partition and couldn't get the WiFi USB stick to work. The manufacturers drivers couldn't be installed because they were ancient, and installing a generic one for the chip didn't work. Had to give up. In windows it's plug and play.

[–] highball@lemmy.world 1 points 3 days ago

Dude, your wifi dongle manufacturer obviously inbox'd their driver with MSFT and didn't mainline their driver into the Linux kernel. When drivers are inboxed, MSFT will maintain them for as long as they are able to. Linux kernel maintainers will do the same when drivers are mainlined into the Linux Kernel. Your dongle manufacturer is the one to blame. Things aren't plug and play because it's "Windows". That's like a Mac enthusiast saying, "My Mac, It just works". It better "just work", there is only handful of devices that are even compatible with Mac. There are plenty of Windows compatible devices that don't have inbox drivers for Win11 and Win10 and guess what, they don't "Plug and Play".

The solution was to just buy a Linux compatible device for the newer kernel you were running. Or, downgrade to a kernel that has support for your device. If it's Windows that doesn't have the inbox driver, you'd have to downgrade the entire OS. Most people don't do that, they just buy a newer device that's compatible with the newer Windows version they are using. Why would things be any different for Linux. Or Mac for that matter. And really, you couldn't just buy a 15 dollar USB Wifi dongle that was compatible with the OS you were using???

If a Windows user buys a Mac, they will just assume they have to buy Mac devices and Mac software. If a Windows user installs Linux, suddenly everything had better work out of the box or the entire Linux eco system is a failure for everyone in the world.

I had the same experience with an old printer: Linux recognized it directly whereas Windows didn't. I wouldn't say that Linux has a strong disadvantage at these things.