Well, "maintainer" is usually a single person job. They didn't write all the code or whatever, just were the gatekeeper to what got added and making sure shit works.
So I mean, it's not great nobody is stepping up, but it's also not like they magiced up the entirety of linux's wifi support single handed, either.

The article isn't entirely clear. I get the impression that the person in question may have been the sole maintainer for some hardware-agnostic parts of the wireless stack (which I'd expect to only need active development when a new standard gets greenlighted; should be bugfixes the rest of the time), co-maintainer of the drivers for some atheros chipsets, and the general oversight/coordination guy, but there are other developers working on specific drivers.
The future of Foss is in corporate time donations for projects that are useful for them. Open software collaboration is one hell of an efficiency gain. Whenever me or my colleagues have dead time I ask them to work on improving open source projects. It's just a few days every few months but it adds up. Also we like to fix bugs in Foss software that affects our customers as we usually fix and upstream them and can bill that to the customer. So the company gets played, the worker gets payed and open source gets funding. No more sole maintainers for life that don't have money to heat their homes because nobody donates. :)
A number of them have written about their reasons- I can't speak for the maintainer this article is about but the general sentiment I've seen from the ones I've been hearing about is that the culture around kernel development is dogwater. Lots of it surrounding refusal to make any space for R4L and shitting on devs working on it, but then also spinning out of that are maintainers likening their quality control responsibilities to being "the thin blue line".
I always say the doom of humanity wonât be wars or something sudden. Itâll be something thatâs been silently happening: the extinction of species and ecosystems one by one thatâs been accelerating in the last 50 years. And now with global warming, itâll only get worse because environments are changing and forcing species out of their homes.
And this is something I donât see getting better at all. Social media just seems to have made people even more egocentric and selfish and actionless too, because ranting about problems online makes people feel like they did their part.
Weâll just witness the world falling apart one disaster after another and watch it as âentertainmentâ on TikTok and Reels, until itâs our turn.
I mean, probably someone at qualcomm will likely take his place? They need drivers for themselves anyway and will probably continue providing them. I have no idea who the contributors of similar drivers are but I'd imagine Intel makes drivers for their wifi chips themselves and contributes them to the kernel since they count as one of the biggest contributors.
It's demographics. Linux contributors & maintainers skew heavily to the older end of the spectrum (and, although not relevant to this point, also skew heavily male).
People who can contribute time to a project for free tend to be older because they are financially and career settled by the time they hit 50s. Raising a family tends not to leave a lot of spare time.
Contributing and/or maintaining a FOSS project < not getting murdered by my wife for "playing on my computer instead of spending time with my family."
It could be some of the most mission-critical work imaginable, but she'd still see it as goofing around because I'm not getting paid, and she requires attention. And I love the hell out of my wife, so happy wife indeed equals happy life.
I used to daily drive Ubuntu some years ago for work/personal use but have been back on Win 10 primarily for the last 4-5 years. I was considering trying to go back due to how much Windows sucks (despite some proprietary software only being available on it) but remembering the trouble I had with some networking/printer drivers and troubleshooting those issues and then seeing this article Is definitely making me reconsider..
It astounds me that people who support linux get personally offended if you say you're not sure linux is for you.
I watched a video where a guy installed linux, and then installed a new desktop environment that caters to touchscreen. He got a bunch of errors. So he said "Ah, that's alright! I'll just bring up terminal"
And then he types
sudo add do willywop bojanga -l -r â§ÂżÂ€ââȘïžâ
And I'm like "ok, hold on. How the fuck does he just KNOW that exact string is what will fix it???"
If you don't speak terminal, that shits confusing as hell.
And now this story is like smokey the bear. "Only YOU can maintain wifi protocols. Seriously. I'm done. It's just you now. The professionals are sick of this shit."
So it's reasonable that non-techies are like "I had some issues before, but now I'll have MORE issues if I comd back.....I better stick with what I kjow works."
Meanwhile lemmy users are like "BOOO WINDOWS!!!! BOOOO I SAY!!! WHY DON'T YOU JUST UNDERSTAND THE THINGS YOU DON'T GET???"
And thus.....you have downvotes for saying logically reasonable things that piss off obsessive types who would downvote each other over which distro is best.
I'm not disagreeing with you, I just want to say, the reason the terminal is helpful in these types of scenarios is never communicated properly in my opinion.
The reason when you ask people for help or Google stuff and get terminal commands back is because they are clear, concise, and reproducible. It's really hard from the perspective of the people helping, to communicate, usually over text, how to navigate UIs that are ever changing and change depending on the users hardware and setup. This is true for windows too, and it's why getting any help beyond very simple troubleshooting will devolve into powershell commands.
As for this scenario, it's just inflammatory on purpose, would anyone mention or care if one person at Microsoft who was a project lead retired after decades of working? There are literally thousands of contributors to the Linux kernel, this is just one of them retiring. A maintainer is only one role in a project and can (and will) very easily be replaced. If not by a volunteer, then in a paid position from one of the many companies that pay developers to maintain the Linux kernel. Regardless, there is already people maintaining the the ath10k, ath11k, and ath12k drivers. This is really just a non issue of a temporary vacancy for one position, the same thing that happens at every single software organization every day.
So two thousands and ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen twenty twentyone twentytwo twentythree twentyfour twentyfive twentynine is the year of Linux on desktop!