3 ms·
Depending on one's tech stack, it can be a lot of work to make a Windows machine work for development. With quite a lot of research and effort, I did it (and w
by blunte 7y ago
Depending on one's tech stack, it can be a lot of work to make a Windows machine work for development. With quite a lot of research and effort, I did it (and without WSL, because in the past WSL had abysmally slow disk IO).
Even so, at least a year or two ago, having Docker and VirtualBox work at the same time was not possible.
The Windows terminal options are nowhere near as good as iTerm or the standard Mac Terminal (which is lower latency than any Windows option).
But even if you get your dev environment working, other daily tasks are more difficult or annoying.
Lack of Preview on Windows is a huge drag. Being able to hit spacebar and near instantly popup a view of images, documents, PDFs, etc. is far far nicer than the options for viewing in Windows.
Finder may not be perfect, but it is more flexible and more capable than Explorer.
Printing a document to PDF is simple and fast in macOS, but it's slow and clunky on Windows.
The same suite of Adobe Creative Cloud tools generally run faster and with less random lag on macOS compared to Windows. And my comparison was between a maxed out Dell XPS 15 of year 2017 vs an early 2014 MBP.
Regarding price, you can't compare a Surface Pro to an MBP on price. The MBP has much higher performance and a more usable format than a tablet with a stand.
If you're happy, that's good for you. But I suspect your use case doesn't subject you to the full chasm of differences between the two devices.
- moksly 7y agoI probably should be noted that my mbp was the 13” i5 version as well, so not exactly one of the high performers.