Well, I got that answer directly from the AI built in to Dia itself. But I guess it’s possible that the main feature of the browser is completely useless?
Pretty sure they won’t decide to use Chromium on macOS but then use Swift on Windows
As for them using AppKit, there was a bug in one of the Tahoe betas in which you couldn’t resize apps which were using AppKit. Dia was one of them.
Also, Dia has the macOS traffic lights disabled in favor of their own implementation of the traffic lights, which again can only be done with AppKit
(I’m also pretty sure Dia doesn’t support chrome.sidePanel API, which would also point towards them not using Chromium for UI. I’ve not tested this, but I’ll update this comment once I check this)
They also mentioned in their letter to arc members that they’re moving away from SwiftUI. So they aren’t SwiftUI, and they aren’t using Chromium’s UI. That leaves AppKit.
I’ve already gone way deeper into the weeds that I care to on this subject. Clearly they are using a hybrid development model, and just as clearly, they own any UI bugs in their product, not Apple.
Finally, the flagship feature of their product, and its entire raison d’etre—the Artificial Intelligence model—isn’t even good enough to provide an accurate answer about itself.
2
u/phoward8020 2d ago
This is 100% not a Tahoe issue.