The value proposition of OSX 10.2 when I switched to a Mac was a clean, elegant UI with that unix terminal for developer tasks. The Windows 10 UI is good, and these days the *nix of real interest is Linux, so the WSL handles that side, so for the same logic, I've moved back in the Windows direction.
Meanwhile, my MacBook Pro 16" has daily kernel panics when it is connected to an external display. It has been reported by many people on Macrumors forums and has been happening for months now. No fix...
I was playing around with it a few months ago and filesystem-intensive operations (like running npm install) were horrendously slow. Has that changed with wsl2?
I’ve been considering picking up a ryzen laptop and running Linux on it, and trying that out as a daily driver. But I don’t have any patience these days for the hacky wifi driver installation dance. And I’m nervous after having a Linux laptop cook it’s own battery when it failed to sleep properly in my backpack. It’s been a couple decades - do Linux laptops just work yet?
WSL2 improves that by offering fast fs on linux side. The boundary is still slow. For example, if you go into /mnt/c and use git status on a large repo it will need to go through the boundary. It is slow (not painful but not pleasant)
My current setup has all my source code on the linux fs (/home/user) and I access them using VSCode remote extensions. The performance is fine. I can't really tell if native macos experience or this is faster. I also tried JB iDEA. It works across the filesystem boundary and even if the access is slow, it does not reflect to real world usage much. But you'll feel it if you look for it.
Another option is to run GUI apps on Linux side and use an X11 server on Windows. This just works fine and they recently announced that the WSL will have built in support for Linux GUI apps.
And it's based on Arch, so you'll be able to take advantage of the excellent Arch software repo and wiki (if necessary).
Linux on laptops is fine nowadays. Recent versions of the kernel vastly improved battery life on Intel. It's much better than it was 10 years ago.
Unfortunately, late-2018 MBP with 560X is apparently incapable of setting the right widescreen resolution (5160x2160 or so), an error that was reportedly "fixed" in 10.14.2 beta... yet here I am with 10.15.4 and nope, you either get everything scaled too big, or you get big black bars on the sides.
I had an old 27" dell monitor that I thought was a blurry POS, until I plugged it into a Windows box and realised it was macOS that was the POS
Also setup asked about some tracking stuff and I said no but haven’t done any research to see how they treat it.
Shutup10 is the best AIO, most tested tool I have found for Windows 10 that doesn't break stuff.
There's also custom ISO's with binaries and entire product suites removed which may break some stuff that runs on Windows 10 (eg requiring the Store for some games) - but I'm not comfortable with the level of transparency custom ISO's offer, so I don't do this: https://ameliorated.info/
My recommendations is to get a copy of Windows 10 LTSC (which doesn't include Candy Crush etc) and run shutup10 on it for your work environment. It's the least risky option for an every day driver.
You can use /quiet and /force flags on shutup10 and create a scheduled task to re-run it occasionally.
I counted six toggles related to tracking that were enabled by default in the OOBE. Forget one toggle and you'll spend 20 minutes digging through Control Panel for it. The "NEW" Microsoft, right.
Not sure how this impacts theory of neglect.
Is it correct that the best folks from any given team at Apple are assigned to new, big initiatives?
Yes, they should. The vast majority of QA should be automated unit and integration tests.
> QA is unnecessary
This is objectively false. Even if you perform 99.999% of all QA in an automated way, you're still going to miss those edge cases, like the infamous daily kernel panics due to buggy support for external USB-c displays that only real humans testing your product in the real world with 3rd-party devices can find. QA is still extremely important, and when companies like Apple neglect it, they end up shipping buggy and disappointing products.
1. mac os has been buggy for quite a few releases already
2. outside of drivers and apps, ios and macos are basically the same kernel and userspace/libraries, so there isnt much to port
mac os at large has a quality problem. I have gotten more kernel panics on my personal and work laptops in the last 6 months than I have on my windows machines in the past 5 years.