3 ms·
For Linux there is supported hardware from Vendors like system76 or similar. You don't expect to run Windows on Chromebooks, Android Smartphones or M1 Macbooks
by danhor 5y ago
For Linux there is supported hardware from Vendors like system76 or similar. You don't expect to run Windows on Chromebooks, Android Smartphones or M1 Macbooks without issues, because these vendors only optimize & test for linux. But since linux is such an open platform, you have a large grey area "vendor didn't test it, ymmv". It may work fine, but you never know if the vendor decided to e.g. ignore standards for reboots and only react to the exact things that Windows does (This also applies to macos running on other devices, but way worse). Most devices have an entry in e.g. the arch wiki describing if they work OOTB, with hacks or some parts just don't.
There are devices where the vendor tries to support linux, e.g. Thinkpads, but if you're using Nvidia it's still a pile of hacks in the background.
I haven't needed to contribute any code myself nor use non-upstream drivers, but the process to use non-upstream drivers is usually pretty streamlined in arch (packaged in the aur).
And since we're in hacker news: Programming things close to the hardware can be a great learning experience, maybe not when done under pressure.
- pjmlp 5y agoThat was why I bought an Asus 1215B Netbook with GNU/Linux support out of the box, an Ubuntu distrubution actually. First the wlan stopped working, because Canonical decided to replace the proprietary driver wih the open source one, however since it was still work in progress, dozen of us had to suck it up with LAN until the open source driver got feature parity. Then my GPGPU experience got degraded from OpenGL 4.1/hardware video decoding to OpenGL 3.3 with the replacement of the AMD driver (fxgr) with the open source radeon one. So in the end, it doesn't matter that much buying supposedly supported hardware.