It's obvious why they wouldn't give a shit about that, though - the Mac is not their main focus. Most companies that make software for PCs are obliged to make at least Windows and Mac versions, and to build an application "The Apple Way," using SwiftUI, and things like "CloudKit" etc. would mean a whole dedicated Mac-experienced design team and Mac-experienced engineering team. This would result in an app that fundamentally works and behaves differently than their app would on Windows, because these operating systems have different conventions and standards.

Now, that would make people like you and me very happy -- but consider it from the big company's perspective. Now instead of supporting a piece of software which has a single set of features and a single consistent (and 'braaanded,' eyeroll) Electron UI (and, mostly, a single set of bugs), you're supporting two completely different apps with completely different UIs. Building a new Important Feature means building it from the ground up twice, and QAing it twice. And customer service needs to be trained to walk customers through both of these different apps which work differently, and some of the customers are so confused, they can't even tell you if they're on a Mac or not.

25 years ago, before cross-platform frameworks existed (other than Java, which wasn't often used to these ends then), that was sort of how they had to do these things, and in practice, the results were either that a ton of hardware shipped with no Mac support whatsoever (wasn't worth it) or with a bare-bones Mac version on the CD that was incredibly low-effort, and clearly still written by people who barely knew how the Mac was meant to work.

This very real phenomenon is why we are cursed with cross-platform everything. The difference between a single cross-platform codebase and even two dedicated good-citizen apps is a vast chasm.