Way back in the olde tymes, I was having trouble with the NIC driver in my Linux install. I posted a question about it on USENET, and got a reply from the guy who wrote the drivers. He asked for some info about the card, then updated the driver to support it.
There used to be a lot of cards based on same or similar chips, but with small differences. That made little changes to drivers common. It's a bit like LCD modules or audio chipset quirks. One driver with tons of little differences depending on what each manufacturer decided to do differently.
Back in the day I was running GLTron on an Athlon 1800+ w/Nvidia GeForce FX 5200 (I think?) and I was running dual monitors. GLTron didn't like using both screens since it presented as a peculiar resolution. So I emailed the GLTron dude and he quickly emailed me a patch that let me run the game across both monitors (bezels not an issue because I was doing multiplayer split screen).
I remember early 2020, there was a small push to bring capes back, before something else took over every discussion. Something about blue jays or crows or something
DRIVER REMOVAL NOTICE ===================== I have been unable to meet support demands for this driver, resulting in unpleasant experience and frustration for everyone involved. Consequently, the driver will be removed from github, effective August 1, 2018. Interested parties are encouraged to clone the driver before that time and to start maintaining it on their own.
Software discoverability on linux sucks so much omg. I was looking for something like coolercontrol for almost forever and I find it now that I dont need it anymore.
Uh, really? I find it to be much easier. apt contains almost everything, and for a niche thing like yours, a Google for aio fans linux came back with the first result of a reddit thread including the above software, and liquidctl which it uses and is all over the place. I have way more trouble finding things for Windows, but maybe that's because 98℅ of my use case isn't gaming.
A lot of Linux drivers are like this - just one or two people maintaining them. They usually eventually mainline the driver rather than having a separate Git repo though.
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.
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.
Had some problems while trying to compile and install a WiFi driver for the first time. Managed to find the email of the driver's creator and sent them a message. They responded a few hours later with incredibly helpful guidance, walking me through the process and enabling me to get it working, all while gaining valuable insights....
To be honest, yes. In general, not just tech or Linux related stuff. You look at humanity and what it has come down to, and then you notice these people... and hope fills your heart again.
The vast majority of my open source projects, I'm the only user. I release it open source because back in the day, GitHub only allowed open source projects if you want to use it.
But another reason is the hope that someone will find it helpful. If not the project itself but maybe the code.
I have one project that has a significant following and honestly it's sometimes very scary because I might not want to keep it updated because of my own interests changing.
The astounding thing is history is full of these types of people when you peel back the “couple great men” narrative of history and actually look at how good things happened, it is kind of bewildering.
Send your thanks directly to the maintainer (preferably email/mastadon/twitter/etc, not a ticket)! Open source maintainers don't get a lot of positive direct feedback.
They're still waiting to be mainstreamed into the kernel. The process of integrating drivers into the kernel is complicated. Coding practices of the coder that wrote the driver play a large part in that. Buggy or badly written code will not get accepted. Not all of these drivers have the code quality that is required in order to be merged with the kernel.