Hacker News new | ask | show | jobs
by chroem 4387 days ago
This isn't 2004. The state of development of the various GNU/ Linux distributions has reached a point where everything "just works". I have yet to see an installation with driver problems. Not to mention that the battery life on my ThinkPad easily compares with, if not exceeds, that of a Windows installation.
2 comments

> The state of development of the various GNU/ Linux distributions has reached a point where everything "just works".

Not really. I'd argue it has actually gotten worse in recent years, unless you enjoy using ancient hardware.

Support for 802.11ac chipsets in particular has been bad in my experience: Intel only works properly with very recent kernels, Broadcom and Qualcomm/Atheros tend to be buggy or they don't work at all. Or they're just barely working and essential features like, oh, using the 5 GHz band, are missing. And these are the three vendors whose chipsets you'll find most commonly in Laptops at the moment.

I guess it's possible I was just very unlucky.

OP also mentions Bluetooth, which I would agree is a bad joke on Linux. The whole stack seems to be garbage.

And of course, if you have a Laptop with anything other than Intel graphics, you might as well not even bother.

All of this – except maybe the Bluetooth part – is of course mostly a problem of hardware vendors being indifferent or even hostile towards Linux, but that does not change the fact that very often it does not "just work". You need to pick your hardware very carefully.

Both my Windows and OSX machines know that if I connect my bluetooth speaker to them, to play the sound through the speaker. Likewise, they know that if I plug in a Logitech USB dongle into the machine, that the sound and mic should go through the dongle.

Elementary is better than most at having some sort of easy to use, functioning bluetooth setup, but every time I use one of these devices I have to go into sound settings and switch them to the device. It's a pain in the ass that other companies have figured out.

This can be fixed by editing your pulseaudio settings:

https://wiki.archlinux.org/index.php/PulseAudio#Automaticall...

I do agree, though, that it is weird that this is not enabled by default.