@schwa insult to injury is that even if you’re motivated enough to build your own, full-fledged replacement - the means of deep integration are gated by internal or private SwiftUI APIs. Almost all the best OSS SwiftUI component libraries that I’ve seen end up resorting to some private API and/or Reflection (which has a massive performance cost).
Like fucking fix it, or let others fix it for you.
@schwa@cocoawithlove Wait, you made a drawing canvas using SwiftUI? Any tricks to share? I’ve been kinda assuming from the API structure that this was a bad fit for SwiftUI and went back to UIKit for that.
Add comment