Another possibility is that macOS actually does proper color management throughout the entire OS - the Windows shell/desktop is simply not color managed and it's especially irritating when you have a wide color gamut monitor.
There is no system level volume mixer, you can't route audio between apps, you can't even monitor an audio output device.
To do anything sane with audio on MacOS requires external applications like Loopback or Blackhole or any of the virtual cable applications.
I don't know what he meant with "audio management", but when it comes to music production, MacOS works way better by default, with system-wide low latency audio and multi-client MIDI drivers.
On Windows, you need to buy a dedicated audio card and install 3rd party audio and MIDI drivers, so that you can finally--assuming you bought the correct gear--get almost the same functionality that every Mac has out of the box.
To be fair, core audio is indeed better default system but any trivial music production involves audio interface, I've never seen a person using direct input to macOS. On daily work, it's pretty much same.
Windows used to be horrid when it comed to music production but that was like almost two decades ago. Been using W10 for quite some time and any basics I need is pretty much there.
On the other hand, hardware taxing when gearing up the equipment is insane on apple hardware, that's why I migrated from their ecosystem. It's a huge drawback for many I believe.
The lack of an OS level volume mixer is one of my biggest day to day frustrations with OS X. Linux is really the gold standard for me though, allowing me to shunt applications around across audio devices on a per app basis when most don't include an output selector.
Sure uh huh. Mac is great when I want to open up GarageBand on my M1 Mac Mini that's connected to my TV over HDMI. It yells at me to change the sample rate to 44.1. I can't do that there is no way to do that. I also can not control the volume using keyboard volume or system OS volume. Mac OS is great! Also the HDR is questionable unless you are using an Apple display which I am not.
Edit: basically what I'm getting at here is one is not better than the other and one is not worse than the other every single OS has quirks and honestly you should just be running one of everything in your house if you need it. Make sure to always have an up-to-date latest Mac and run WSL 2 in Windows 10 or 11.
gfx.color_management.mode = 1 only worked vaguely correctly if all of your monitors share the same color space (or you only have a single monitor). Videos also weren't color managed, and there still existed some situations where colors would still be incorrect. (see: https://cameratico.com/tools/web-browser-color-management-te...)
This change effectively sidesteps the issue by making everything render to sRGB, and telling macOS that Firefox's windows are sRGB only.
> effectively sidesteps the issue by making everything render to sRGB
Wow, that seems ... really unfortunate? So on macOS, if I open a nice photo from a friend that's tagged with AdobeRGB, Firefox will downconvert that to sRGB? I hope they don't bring that change to any other OSes!
You're right that mode 1 is flaky and could use some improvements (video, canvas elements, av1 which is treated as video by the decoder...) but converting wider gamut graphics down to sRGB seems like a clear step in the wrong direction.
By the way, Firefox passes all the tests in the article you linked to for me.
Honestly, I'd rather have consistent and accurate colors across multiple monitors even though it would be limited to sRGB. Most content on the Web is for sRGB anyways, so it's not like much was lost.
It's still much better than Windows though... I clamp my wide gamut monitor to sRGB because Windows is so infuriatingly inconsistent.
Are you using the beta? If not, that's expected unless you have the mode=1 setting I mentioned in my top level comment. I have that set on Linux and everything works as expected. (I haven't tested this on macOS at all so it's possible the setting isn't even functional in Firefox 88 for Mac.)
Can confirm - in a large React app, SVG Font Awesome icons constituted a disproportionate amount of time spent rendering. Switching to the icon font dramatically improved performance.
NVIDIA pushed the 3080's stock performance a little too high up the perf/watt curve. If you limit it to the TDP of the 2080 Ti, you lose 4% performance but you get much better efficiency: https://www.computerbase.de/2020-09/geforce-rtx-3080-test/6/
