3 ms·
I envy your knowledge and ambition. What you've done is beyond my capabilities. But I think the crux of the problem is that people are trying to run commodity
by reaperducer 7y ago
I envy your knowledge and ambition. What you've done is beyond my capabilities.
But I think the crux of the problem is that people are trying to run commodity software on custom hardware. That just won't work long-term.
Linux is commodity software, that runs great on white box commodity hardware. macOS is custom software that runs great on custom hardware. Each has its place and purpose.
It's like driving a car on train tracks. Yes, it will get you somewhere, but it's not the right match of tools and environment. And it's inevitably going to be a bumpy ride.
- banachtarski 7y agomacOS runs horribly on custom hardware, it just runs better than other commodity software. Any application that pushes frames/performance would do better on Linux/Windows on the equivalent amount of silicon. What's missing because the hardware and drivers is so closed is the feedback loop between application/game devs and the vendors. If I have an issue with what I'm building, I can hop into a chat and immediately talk to Nvidia/AMD/Intel folks/etc. In some cases, they share code, in some cases they release a driver update. In pretty much all cases, the code I'm working on gets better. Apple lacks this feedback loop, and their drivers are garbage.
- danieldk 7y agoApple lacks this feedback loop, and their drivers are garbage. There may be exceptions, but I never had anything like the graphics glitching that the Nouveau drivers had or known problems that would lock up Intel GPUs every one 1-2 days or consistently in some workloads [1], or broken Intel WiFi drivers. The recent Intel driver problems literally took months 4-5 months to fix, while they show-stopping errors were in an LTS kernel release that was rolled out in various distributions. If I have an issue with what I'm building, I can hop into a chat and immediately talk to Nvidia/AMD/Intel folks/etc. In some cases, they share code, in some cases they release a driver update. You mean like asking NVIDIA for Wayland support following the same standards as everyone else? That worked well. Everyone's drivers are bad, but I don't believe for a second that Apple's are measurably worse than Linux or Windows drivers. [1] https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_Frequent_Intel_GPU_Hangs_In_Recent_Kernels https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_F... [2] https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.6-Broken-Intel-IWLWIFI https://www.phoronix.com/scan.php?page=news_item&px=Linux-5....
- computerex 7y agoIt goes without saying that OSX has the worst driver support out of Windows/Linux/OSX simply because OSX supports the smallest range of devices it will run on. Windows runs on hardware from a wide range of OEM's, whereas OSX only supports hardware produced by Apple. Try running a hackintosh and you'll very quickly see what I mean. Linux driver support used to be garbage but it has gotten quite good lately. User friendly distributions like Ubuntu typically work out of the box now.
- danieldk 7y agoNow we have gone from macOS drivers are garbage to macOS has the worst driver support. Which is a completely different statement. Also it's one that is hard to disagree with -- macOS is only made to run on Macs.
- banachtarski 7y agoI'm absolutely NOT including open source drivers in my assessment. I'm specifically talking about drivers written by vendors who unsurprisingly do a better job targeting their own hardware.
- danieldk 7y agoThanks for the clarification!
- wpietri 7y agoAll hardware begins as custom hardware. Commoditization happens when a standard is published and other people start making it. But there's nothing intrinsically more special about Apple hardware than anybody else's. The problem here isn't a mismatch between the specialness of hardware and the openness of the OS. It's that Apple is hostile to people writing an OS for their hardware, so they don't share the kind of information that's available for both commodity hardware and custom but well-documented hardware.
- codemac 7y agoGNU started with a printer that couldn't be modified. Mac's are not as custom as you think, and it wouldn't be that hard for them to give out enough information to get Linux running on MBPs. In fact I hope we have a large community of folks making sure we can reverse engineer everything. LLVM and the likes are great compilers, but Apple is leading exactly where Stallman warned about - a computer you can't write software for.
- Dunedan 7y ago> I envy your knowledge and ambition. What you've done is beyond my capabilities. I mostly did just coordination and verification. The only code I contributed are very small workarounds for the NVMe controller and webcam. Nothing noteworthy. The serious work of reverse engineering and implementing custom drivers was done by others which are to be applauded much more! There is one person I want to point out in particular and that's roadrunner2 [1] who took the existing input driver for the 12" Retina MacBook and not just made it work with the MacBook Pro's, but also implemented support for the TouchBar and ambient light sensor. As this driver is based solely on reverse-engineered workings of the input system and Apple does very unique stuff there this was so much effort. Including very subtle, but surprising bugs (e.g. [2]) which could've easily avoided if documentation would've been available. roadrunner2 is also the one to applaud for bringing the support for keyboard and touchpad to mainline Linux. As that not just required an input driver, but also touched other subsystems and required serious refactorings that was quite an achievement as well and is the reason keyboard and touchpad even work out of the box after booting a Linux distribution nowadays (although it's still not perfect as some distributions don't enable the applespi driver yet). [1]: https://github.com/roadrunner2/macbook12-spi-driver https://github.com/roadrunner2/macbook12-spi-driver [2]: https://github.com/cb22/macbook12-spi-driver/issues/53 https://github.com/cb22/macbook12-spi-driver/issues/53
- teleforce 7y agoThe days of globalised custom hardware are numbered. Most of the hardware that are used to be customised as we know then, are actually now a commodity. For example, networking vendors always custom made (i.e. ASIC) their networking hardware especially their high end flagship products but not anymore [1]. Most of them now are just targeting commodity hardware since in the long run customization is not technically and economically feasible at the global scale. [1] https://www.nextplatform.com/2018/06/20/a-deep-dive-into-ciscos-use-of-merchant-switch-chips https://www.nextplatform.com/2018/06/20/a-deep-dive-into-cis...