Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm pretty happy with Linux on my desktop - I use it for development, making music (Bitwig - I have a full studio hooked up to it, using an audio interface, a midi interface, a control surface, a variety of midi controllers, and sufficient VSTs, all over out-of-the-box ALSA), CAD (qcad), voip (Jami), and general web related stuff. Wifi hasn't been an issue for me since the days when you used iwconfig from the command line, which was what, 2006? Network Manager is generally good software (otoh I don't love systemd-resolved's ownership of DNS, and have had intermittent issues with that in the past couple years.) I use my wife's mac occasionally to upgrade firmware on my hardware synths, since synth vendors don't tend to support linux.

On one of my laptops, there's been some intermittent nvidia driver issues (leading to screen tearing), but they're only an issue on one of the compositor options in KDE (I don't remember which). I also have it installed on an intel nuc (which is acting as a print server for an old/reliable but unnetworked laserjet), an MS Surface go, a chromebook, and a few older laptops.

In many cases you buy a windows computer with the OS pre-installed. That almost never happens with linux (I will probably buy my next laptop from system 76), so it's always smart to either run a live boot to check on driver/hardware compatibility, or do a little digging up front to find out the state of hardware support for the configuration you're planning to build. You can certainly end up with hardware that isn't supported.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: