If you mean due to lack of C++ for doing GUIs, Google and Microsoft have also long left C++ to the dust, in what concerns GUI frameworks.

Even Microsoft, for all its C++ use, has never produced anything better than MFC to this day, and only Windows team cares about XAML C++, others rather use React Native or Webview2 alongside C++.

It is up to third parties to use frameworks like Qt.

▲

isodev 12 hours ago | parent [-]

I mean specific APIs and targets are required to be written in Swift (e.g. widgets) + iOS/macOS dev tooling is hostile to any attempt at bringing in your own preferred language stack. I wouldn't be surprised if Apple's "glasses" or other tiny devices make it even harder to stray from the "one true path".

	▲	Klonoar 9 hours ago \| parent \| next [-]
		How is it hostile? Calling ObjC via your language of choice is like the easiest thing possible, solved multiple times over. Signing and notarizing outside of Xcode is also a solved problem. IME people bitch about this but when push comes to shove just don’t want to do the required work, typically on flimsy grounds. It’s just not that hard. The increase in Swift-only frameworks will eventually be a problem but it’s typically not a blocker right now.
	▲	pjmlp 12 hours ago \| parent \| prev [-]
		No different on Microsoft and Google platforms. Those that think it shouldn't be, end up yak shaving trying to bring UNIX and C concepts to platforms that no longer care about that.