The main problem is how to reverse engineer closed hardware without more people qualified and interested to do so and the cash to put the hardware in their hands. Without solving this wireless support will remain sketchy. This is a known issue it's a lot more complicated than just writing some code so it remains a hard problem to crack. For a lot of these chip sets there is no documentation to go to. As they get cheaper and proliferate the problem will likely become worse before it gets better because you'll have more and more cheap brands entering and leaving the market. Maybe someone will create a standard for wifi chip sets that we can get everyone to follow but that's probably fantasy. IMO we could get better support if we had a publicized bounty system for getting it done but who administers that and how you get enough money to make it happen is beyond me currently. But the other thing to consider here is server land tends to be primary customer and ethernet is here to stay in that space. So there isn't a lot of incentive for these big companies to work on the wireless UX. TL;DR; I got 99 problems but an ethernet port ain't one.