I've never had issues setting up dual boot. It works fine and I can read/write NTFS if needed from Linux or just rely on Dropbox for simple stuff. The problem is it is too inconvenient to reboot so I usually just run Win 7 from a VM inside Linux. I also had a number of issues with Windows being glitchy (this persisted on three different Thinkpads with Windows 7 and, back in the day, Windows XP) and a pain to maintain, which is why I use Linux as my primary desktop OS.
I also don't have a problem with power management and suspend on Linux, though I know it probably isn't as good as Windows. I don't use hibernate so I'm not sure if it is awful. For my next PC upgrade I'm not getting a laptop, however, since I hardly ever travel with it...
I like OSX fine enough, too, but I rely on a lot of Linux tools so I have no real reason to have an OSX machine.
If I were forced to use OSX or someone gave me an OSX machine I think I would get along fine and be productive, though. I can actually get along fine in Windows, too, but it is somewhat frustrating and slower for me to get things done.
Not that Linux is perfect, but I'm used to it.
It's exactly the same the other way around for e.g. audio and video editing on OS X vs. other platforms.
I have different machines running different linux distros, so I'm familiar with all the popular package managers (apt-get, yum, pacman), and I must say, Homebrew is really my favorite.
Binary packages are a wonderful thing and a package manager that doesn't support them out of the box isn't a usable solution for the things I do.
Homebrew also doesn't manage OS X itself, which is something I really prefer about apt-get.
The benefit of apt-get source is being able to read the correct version of the source code of any part of the operating system to debug a problem, not necessarily building from source.
Wrong. Homebrew has so-called "bottled" binaries that get "poured in" unless you tell it to build from source or use a flag mandating a custom build.
I'm using the former and it works pretty well for me. Though I wish either of those would use apt-get like Fink did.
It seems my experience with computers has been radically different from yours.
The only kernel I've ever had problems with is the NT kernel, and one of the reasons I stick with Apple portables is that they're generally the least buggy devices I can find.
If you really want to try Linux, you need to buy a computer designed to run it, or at least vet your hardware before a purchase. I haven't bought a computer with a Windows license attached in over a decade because that isn't buying a Linux capable machine - its buying a Windows machine you might be able to run Linux on.
My most recent system was a build I made last year and I vetted every part for LInux support (and boy, did it take a while to verify Asus z87 motherboards had a working EFI that could boot a linux kernel, albeit they have a busted EFI shell and can only have one EFI boot table entry).
If that is indeed the case I think it would be tremendously important to fix that.
Are there better sources to read up on this, or is the controversy a bit over blown?
You can't blame Linus for that. If a company doesn't want to push what is often only a few hundred lines of C to make their devices work under Linux, thats their right. But you can't blame the ecosystem for the companies choices not to support it. It is like buying Nexus 7 and bitching about how Windows doesn't run on it.
I have no problems with UEFI whatsoever; in fact, I think it's a nice improvement to the dated BIOS technology. The Microsoft thing called "Secure Boot" might pose a problem, but I never activate that anyway.
People need to stop confounding UEFI with Secure Boot.
There is a distinction here - Linux, the kernel, runs on pretty much every CPU in the universe. If it is presented with any CPU and chipset ever made, it can run on that.
Your PCI devices, your USB devices, etc are not guaranteed to have Linux drivers for that hardware. And if the producers of said hardware don't release driver documentation or support a Linux driver directly, you can't blame the Linux community for not being magicians that can force private companies to bend to their will.
Hell, Broadcom - one of the worst FOSS companies, in the same class as Nvidia for the longest time - is finally producing scant upstream NIC drivers. They support a tiny fraction of their product range, and they have another 2 proprietary drivers on top of those for Linux and those don't work either, but the situation is improving.
But that is all you can do. There is no "sit down and code" answer for undocumented motherboards, bad EFI implementations, and a 15 button mouse with a 50MB proprietary driver on Windows. Well, the latter actually you can just wireshark the usb bus and get all the signaling for the buttons, but that is a lot of work to do what the company itself could have done in minutes (publish the opcode manual they obviously have on the thing).
You can't "fix" people to stop them from talking out of their ass.
https://www.dell.com/us/business/p/xps-13-linux/pd
There are a few others. Its not really hunt, you just have to use a Linux laptop brand or find an OEM that sells bare notebooks.
Saved a tidy sum compared to shopping locally. Just pay attention to KB layout.
Now I have a MacBook with OS X. It combines the things I want from Windows and Linux, so I have no need to change OS. If I really need Linux or Windows for something, hardware virtualisation makes things easy.
And that is Ubuntu (12.04 LTS) noob friendly edition on standard Intel Centrino hardware.
> Noob friendly Linux distributions like Ubuntu provide excellent support of all the points you mention.
While it is not apple to apple reason, this part is why I actually moved away from Windows -- yes, resume and hibernate (mostly) works on Windows, but with a great pain of waiting forever for that process to complete.
I have a small Asus netbook for traveling with Ubuntu LTS, bought from Amazon with Linux already installed.
My home system, a more beefy laptop, has Windows with VMWare for Linux related stuff.
Since 1995, my first Linux experience, there are things that hardly have changed in terms of hardware support.
My latest issue is trying to make MTP support work properly.
I can't open windows on AWS when someone digs up my Internet connection...
I settled on using Windows as a host OS[1] and use Linux on VMs because to be fair, Windows power management, suspend/resume and hibernate and driver support is miles better i.e. it actually works more than once. Oh and they really don't fuck up the kernel every 2 minutes like on Ubuntu and don't throw out buggy shit like Apple do.
I used a 2011 MBP for the last 6 months or so however (with virtualbox) and I had to go back to an older and slower T400 as it was more reliable as well.
So virtualbox on windows 7 it is. And it works really well. I'm pretty happy and I'm a picky as they come when it comes to hardware and software.
On my desktop (a Dell T3500 with piles of RAM), it's 8.1 with Hyper-V with Linux in it as that works pretty damn well too.
Is suspect the problem here is users rather than hardware and vendors.
[1] On my Lenovo T400.