4 ms·
One thing I have to say, in general to many of the posts here about the state of linux, is that linux is just the kernel, and the vast majority of issues people
by arminiusreturns 7y ago
One thing I have to say, in general to many of the posts here about the state of linux, is that linux is just the kernel, and the vast majority of issues people tend to have is due to one or a combination of distro choice and DE/WM choice. I went linux exclusive personally and professionally a few years ago and have nothing but good things to say about it, but far too often I see stuff complaining about linux when it's really not linux per se, but the other software choices.
So, protip, if you are having issues with things like multi-monitors, etc, start out by trying a different DE like awesome/i3, xfce, etc, rather than the big 2 (KDE/Gnome), and if that fails try a another distro (such as Manjaro).
I almost always use Manjaro these days because the hardware detector is second to none, but I used to distrohop habitually and if you get a new laptop it's almost a requirement to try out different distros until you find the one that just works, and this especially applies to MacBooks, which I used to triple boot but started doing linux only on because sometimes it's easier to get a macbook approved in some companies than the equivalent hardware normal laptop.
One side benefit of going linux only is that I have, besides gaming, almost completely GPLized my stack. Plus, I believe if you are managing systems you should be running the OS those systems live on. EG if your core systems are debian, you should have a debian install somewhere that you interact with daily. I can't tell you how many times I've had to help devops people recover from things like MacOS text bunging or outdated bash related problems. I think they should be doing the dev work at least in a container (lxc, etc) on what they are working on instead of the native system.