Linux
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:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Because the driver is the glue code between the device, and the operating system. What happens when the kernel changes, or needs to change? Then the driver on your devices don't match up with the kernel anymore. A lot of Windows folks think Windows has some sort of stable interface and that's why Windows is backwards compatible. But it's untrue, Windows has inbox drivers, just like Linux has driver's that build with the Kernel. Any driver that reaches inbox status get brought into the Windows source. As the Windows kernel changes, Microsoft engineers update all the inbox drivers to match the new kernel changes. When companies don't get their driver inbox'd, they are responsible for keeping up with the kernel changes. Some devices eventually get left behind.