It’s mind boggling just thinking that things like this depend on the effort of one or two guys… while on the other hand, it’s not so uncommon that a team of engineers and developers fails to deliver a working (mostly) bugfree product.
I think management is who is responsible for the shitty decisions, as always… and, in general, just holding the team back.
What’s the deal with Nebraska? Are people from there like really polite and helpful?
There’s nothing to do in Nebraska except drink and maintain Linux drivers
It’s just a random location that was chosen for the joke, it’s in the middle of nowhere
The thing with drivers is that the hardware they’re written for doesn’t really change. A particular network card is always going to behave the same way. Once the driver works well, it’s pretty much complete, and the only changes that are needed are bug fixes, updates to handle new firmware, or adjustments if the kernel changes some implementation detail of how drivers are used. There could be months or years between updates to the driver.
Some manufacturers have great first-party Linux support. Intel is a good example - they contribute a lot of code to the kernel, and their drivers are maintained by employees.
There could be months or years between updates to the driver.
Yes, but someone still has to implement that “a thing or two” in it every few years.
Some manufacturers have great first-party Linux support. Intel is a good example - they contribute a lot of code to the kernel, and their drivers are maintained by employees.
Agreed. But, to be honest, most aren’t. Just take a look at Realtek. There’s bound to be at least one chip made by them on your board (in most cases, two, LAN and audio, two very crucial pieces of hardware).
Realtek NICs are junk (even the buggy Intel I225-v chip is better) so I try to avoid them, but I honestly haven’t ever checked which sound chip my motherboard uses. I’ll have to check if it’s a Realtek one. Realtek is generally the lower-end manufacturer for cheaper products.
