How and why I transitioned to Linux, and how you can too

Re:How and why I transitioned to Linux, and how you can too by AnIdiotOnTheNet on Saturday January 19, 2019 @11:10PM (#18950987)

Getting the driver from the manufacturer directly is somehow involving a middleman in your world, but having that vendor have to submit kernel patches and hope they're blessed by the community, merged, and eventually distributed by the distros isn't?

> No more waiting for Microsoft to roll out fixes; you can apply your own changes yourself.

You don't have to wait, since vendors can roll out new drivers. And what's the equivalent on Linux? Pollute your system with an unnecessary kernel dev environment and compile from source. Personally, I think having to resort to that for such a simple operation when it is almost 2020 is a gigantic failure.

[ Parent | on HN ]

Re:How and why I transitioned to Linux, and how you can too by bubblethink on Saturday January 19, 2019 @11:22PM (#18951057)

I mean that is essentially how all science is done. It has to go through peer review for it to be worth anything. So that is a strong point. You second point is also an exaggeration. You typically wouldn't compile anything (unless you want to). All supported distros will provide binary updates.

[ Parent | on HN ]

Re:How and why I transitioned to Linux, and how you can too by AnIdiotOnTheNet on Saturday January 19, 2019 @11:30PM (#18951091)

> I mean that is essentially how all science is done.

Installing software shouldn't have to be a formal scientific discipline. It isn't rocket science unless you make it rocket science so you have an excuse to invent package managers.

> All supported distros will provide binary updates.

Eventually. On their own schedule. If you want (or need) the latest driver as soon as the vendor says it is ready, you'll be compiling. Otherwise you have to wait for the kernel maintainers, then the distributors.

[ Parent | on HN ]