I'd be interested to hear what kind of problems you had with Linux drivers on a desktop, that isn't something most of us, Linux users, had major problems with for almost a decade.
Even Pascal GPUs are supported, unlike on a Hackintosh.
I have a desktop that's been running strong for over half a decade with Windows 7: core i7-920, dual GeForce GTS 250 graphics card (identical, no SLI bridge). It's hooked up to 3 monitors with 2 on the first card, and 1 on the second. On Windows, this works completely fine.
On Linux however, I only have one ancient version of Linux Mint Debian Edition with an old version of the Nvidia drivers working. But only in a configuration where each screen is a separate X session, so no moving windows across monitors. That's fine by me, but I don't use this install anymore because everything is out of date.
On any recent distro of Linux, the default is to use Nouveau drivers which can get all screens to activate after messing with the configurations. BUT, I either run into screen flickering, invisible mouse cursor, instability, or poor performance. That is issue #1. My thinking is ok, back to Nvidia drivers. They install fine, but I cannot get any combination of settings to activate all 3 screens either as one X session (third screen never works) or as separate X sessions like in my old install (depending on the DE I choose, either no DE is launched on the other monitors, or they do launch but the only way to run programs on the other X sessions is to manually configure the DISPLAY value to those screens and launch the program in a terminal).
Ignoring the fact that I had to give up on using the GUI configuration programs and edit xorg files like I was back in the 2000s, can you figure out a way to get my environment working in a sane manner?
> as separate X sessions like in my old install (depending on the DE I choose, either no DE is launched on the other monitors, or they do launch but the only way to run programs on the other X sessions is to manually configure the DISPLAY value to those screens and launch the program in a terminal).
the issue is not with the drivers, but with whatever DE you want to use. Since the vast, vast majority of people nowadays do not run multiple X screens, there isn't a lot of interest on the part of desktop environment coders to get them working (also because likely they don't have that hardware themselves and so can't try it either)
I personally also run two separate nvidia cards with two separate X screens on them, I run i3 but have had to patch several things to get it to work well enough for myself, it was doable for me to patch i3 due to having spent many years deep into X11/Xt way back, but definitely not something the average user could do and not something useful enough to a large enough number of people to warrant including in it for everybody
A desktop environment coded to expect that it's run once per computer in general won't like being launched twice in parallel (one for each screen), if you want something easy I suggest doing something like running KDE on your primary card and Gnome on the other: you will very likely have to mess with your .xinitrc to launch each separately on :0.0 and :0.1 but it should be doable
I only mentioned the separate X session part because that has been suggested as a "workaround" for over half a decade; hence why I even have that setup on my old install. I was simply anticipating someone posting a response claiming that it would work with such a configuration as I know the inevitable answer (I revisit trying Linux on this computer maybe once a year).
> Since the vast, vast majority of people nowadays do not run multiple X screens, there isn't a lot of interest on the part of desktop environment coders to get them working (also because likely they don't have that hardware themselves and so can't try it either)
Yup, I get that it's uncommon. It's just sad that what used to work years ago has regressed and simply does not work at all anymore. I also considered doing the .xinitrc thing you suggested, but stopped myself from wasting more time as it would just result in a frankenstein DE that wouldn't be very usable (Gnome & KDE are quite far apart in usability philosophy).
(edit: Also remember that to a non-technical user, they would simply try what the GUI suggests. Nvidia defaults to separate X sessions across different cards. Since DEs don't work with that configuration anymore, that would appear no different than a driver issue to the end user.)
> This constant regression in features is what I dislike most about Linux lately. Eternal September in software form.
This is what pushed me from using Linux full time for almost a decade to jumping ship to Apple a year ago. That and people like AsyncAwait who never seem to respond to people like me who post concrete real world problems despite claiming everything negative is FUD.
I understand why a Mac OS X virtual machine might not be completely compatible with Apple's overall business model but perhaps something available through the Apple developer program? Something, anything, would be nice.
I believe that there's a DLL patcher for Windows VMware that allows OS X guests. Back when I tried it last time, it worked nicely but then again I only used it for creating USB install media for repairing / reinstalling broken Macs and didn't require stuff like high-performance USB or GPU acceleration.
- Trackpad is awful and all the synaptics software and tweaks and configs I've tried can't make it work half as well as a MBP trackpad - graphics switching + sleep + power brick replugging + lid closing doesn't work ever - high power usage unless powertop --autotune is run, which breaks USB replugging and causes more havoc with sleep - mfg defect with the ribbon cable under the space bar causing the space bar to be almost unusable. Required a new keyboard and me tearing the whole thing apart to fix
The screen is gorgeous though (thin bezels + 4K IGZO + capacitive touch which I don't need) and the hinge works well even when touching it. Build quality is OK but not micron-level perfect like MBPs (the seam where the metal meets the bottom shell is off by a tiny bit and catches my finger). The power brick is bigger than an MBP equivalent and they're not ubiquitous as the MagSafe2s now are. Having real USB ports is nice, since I hate the USB dongle I have Velcro'd to the USB-C power cable for the tbMBP.
It also doesn't run Mac OS, which FWIW on the 2016 tbMBP fares about as well as the Dell with re-plugging two 4K DP USB alt-mode adapters -- I end up hard-powering the MBP >50% of the time since the internal displays and external displays won't show anything, even though the stupid touch bar lights up.
I got the Dell used on eBay for about half of retail, which is about what I consider it to be worth, while I consider the 2015 rMBP to be worth ~$1600 and the 2016 tbMBP much less.
The trackpad has problems jumping about occasionally, the wifi is unreliable to say the least (linux, but I think also on windows) and the fan spins up sounding like it's catching on something. The audio quality is atrocious.
Oh and really bad coil whine as well, a problem I've never had with macs.
However, it's fairly alright and significantly cheaper.
https://www.amazon.com/gp/product/B00RCZ4I6S/ref=od_aui_deta...
Anecdotally, I've got Fedora on mine, and I noticed a huge difference in the trackpad responsiveness when I switched from the Synaptics driver over to libinput. Palm detection got way better, for one thing.
But keyboard on my dell is leagues ahead of mbp hands down.
Not wanting the cursor to stall and then jump around is not personal preference though.
Gestures work perfectly, the cursor never jumps around either - unlike other laptops with crappy touchpads.
Touchbar MBP's keyboard is a huge downgrade and I agree that the XPS 13's keyboard is superior. I have no idea why Apple ruined one of the best keyboard in the industry with the Touchbar range.
[1] http://www.alphr.com/laptops/1002278/dell-xps-13-vs-macbook-...
[2] http://www.itpro.co.uk/laptops/21797/macbook-pro-15in-v-dell...
The only place where the XPS 13 is inferior in terms of build quality, so far as I can tell, is coil whine. I believe they've fixed that in the most recent versions.
Also, even though it's not a big deal I'd rather not have a touch screen at all as I do on the XPS. It's useless, and registers touches when I close the lid (I prefer not to suspend if I'm just walking from one room to another)
Edit: I should note I use Ubuntu exclusively on the XPS 13. I don't know what the trackpad is like in Windows. Presumably it's comparable.
Also my XPS13 is 2 years old and the "carbon fiber" cover started to disintegrate along the edges. The screen hinge is a bit loose so it wobbles a bit with movement.
Other than that it's fab :)
The general shoddy build quality of most manufacturers, combined with the fact that Apple would likely sue the pants off of trackpad "clones", is my reasoning for why all other trackpads are just functionally absent when compared to Apple.
I have the max-spec new 13" Touch Bar MBP, and it's a terrible laptop. The keyboard is so loud I have been banned from using it in the bedroom at night - a practice I have been doing for the entirety of my marriage. The TouchBar is so useless at night and for development work (where I extensively use ESC and F-keys) that I literally have to put another keyboard on top of the laptop.
So, please, give me MacOS running on a similar-spec non-Apple laptop with a proper, quiet keyboard and I will thank you form the bottom of my heart (and my bedroom).
I will say that the Track Pad on the latest MBP is really very nice.
My hackintosh (currently on my second one, it's a 2012 i5 machine) has less stability and driver issues than Windows 10 on the same hardware.
Hackintoshed OS X (10.9 Mavericks in this case) just treats the card as an 9600M GT and runs it without issue. No panics, no lockups, and no performance hit.
Made me think about the argument that Windows needs to support so many hardware combinations that <X> which I seem to remember sometimes hearing :) Although, to be fair, I obviously bought rather mainstream components and am not running RAIDs etc.
I've found that only by avoiding drivers direct from the manufacturer do you ever achieve true stability in Windows.
Loving the Hackintosh, but I lose a lot of my life anytime I want to change something.
And for dot dot releases, I had a terrible time with updates because I really, really wanted a RAID 1 for my system drive (using an approved hw RAID card). Turns out, this is a very rare setup, but one that made upgrades between minor macOS releases very tricky, with the tools provided. And I got almost no help from the forums (because no one there had done it).
After two years, I gave up and got a Mac Pro 6,1. And, even though the video card I had was very beefy, Lightroom performance was much better with the nMP, I guess because Adobe supported the standard video card in the nMP but not the one in the hackintosh.
That being said, the more I used it, the more it made me want Apple hardware. The keyboard, trackpad, screen, magsafe, etc.
I'm now using a MBA 12" and could not be happier.
> Note that setting up a hackintosh will probably cost you at least a day the first time
I think they're fun to tinker with (reminds me of building a Linux machine circa 1999) but unless your time is free they're usually not a cost savings (though in your desktop use case the numbers may work out)
That being said, I have a MacBook Pro as well, and it wouldn't feel right to install macOS on a Dell notebook. Considering the value macOS has for me, and other benefits of MacBooks (build quality, trackpad, possibly screen although I haven't seen the DELL), I feel the price is fair and I don't want to undermine those creating these excellent products – you may even want to consider what today's DELLs would be without Apple. I doubt that we'd have seen retina screens without their lead.
On the Desktop, where I do a lot of work in tensorflow, Apple just doesn't give me a choice. The graphics and CPU options aren't available, and if they were, it'd be almost a 5-digit sticker price. It's probably a net positive for them because it lowers the chances of me leaving Apple to run an illegal copy of macOS.
Note that setting up a hackintosh will probably cost you at least a day the first time, and anything from "it just worked" to another day every time you want to install an update. For a professional with opportunity costs, it's a losing proposition for notebooks. The hackintosh community is also extremely unprofessional, with many tools still on sourceforge, some doing strange things that appeared to me to be attempts to get paid for work incorporating GPL code, documentation being almost exclusively of the walkthrough-type (i. e.: "set uia_exclude=HS12" with no explanation to be found anywhere as to what "uia" or "HS12" are), and the worst user interfaces ever invented by anyone not working for a printer manufacturer.