MacOS is an excellent workspace operating system, largely due to its near-POSIX compliance and the fact that it has access to the enormous body of tools developed for UNIX-like OSs. For development work in particular, it can use the same free and open source software, configured in the same way, that Linux uses. Aside from the DE, a developer could swap between Linux and MacOS and barely realize it. Everything from Node, to Clang, to openJDK, to Rust, along with endless ecosystems of tooling, is installable in a consistent way that matches the bulk of online documentation. This is largely in contrast to Windows, where every piece of the puzzle will have a number of gotchas and footguns, especially when dealing with having multiple environments installed.
From a design perspective, MacOS is opinionated, but feels like it’s put together by experts in UX. Its high usability is at least partially due to its simplicity and consistency, which in my opinion are hallmarks of well-designed software. MacOS also provides enough access through the Accessibility API to largely rebuild the WM, so those who don’t like the defaults have options.
The most frequent complaint that I hear about MacOS is that x feature doesn’t work like it does in windows, even though the way that x feature works in windows is steaming hot garbage. Someone who’s used to Windows would probably need a few hours/days to become as fluent with MacOS, depending on their computer literacy.
People also complain about the fact that MacOS leverages a lot of FOSS software, while keeping their software closed-source and proprietary. I agree with this criticism, but I don’t think it has anything to do with how usable MacOS is.
I’m not going to start a flame war about mobile OSs because I don’t use a mobile OS as my primary productivity device (and neither should you, but I’m not your mom). The differences between mobile OSs are much smaller, and are virtually all subjective.
Sure.
MacOS is an excellent workspace operating system, largely due to its near-POSIX compliance and the fact that it has access to the enormous body of tools developed for UNIX-like OSs. For development work in particular, it can use the same free and open source software, configured in the same way, that Linux uses. Aside from the DE, a developer could swap between Linux and MacOS and barely realize it. Everything from Node, to Clang, to openJDK, to Rust, along with endless ecosystems of tooling, is installable in a consistent way that matches the bulk of online documentation. This is largely in contrast to Windows, where every piece of the puzzle will have a number of gotchas and footguns, especially when dealing with having multiple environments installed.
From a design perspective, MacOS is opinionated, but feels like it’s put together by experts in UX. Its high usability is at least partially due to its simplicity and consistency, which in my opinion are hallmarks of well-designed software. MacOS also provides enough access through the Accessibility API to largely rebuild the WM, so those who don’t like the defaults have options.
The most frequent complaint that I hear about MacOS is that x feature doesn’t work like it does in windows, even though the way that x feature works in windows is steaming hot garbage. Someone who’s used to Windows would probably need a few hours/days to become as fluent with MacOS, depending on their computer literacy.
People also complain about the fact that MacOS leverages a lot of FOSS software, while keeping their software closed-source and proprietary. I agree with this criticism, but I don’t think it has anything to do with how usable MacOS is.
I’m not going to start a flame war about mobile OSs because I don’t use a mobile OS as my primary productivity device (and neither should you, but I’m not your mom). The differences between mobile OSs are much smaller, and are virtually all subjective.
You’re welcome.