Gosh Darn SwiftUI
Sarun Wongpatcharapakorn (via Andy Bargh):
All the answers you found here don’t mean to be complete or detail, the purpose here is to act as a cheat sheet or a place that you can pick up keywords you can use to search for more detail.
kateinoigaku (Soroush Khanlou):
Only Apple knows the actual implementation. But it’s certain that AttributeGraph.framework has its own reflection system.
I said “I’m looking forward to your great libraries using metadata” in try! Swift but I had never thought Apple do it, I think Apple started to use metadata because ABI stability was built since Swift5. In fact, ABI stability brings us great benefits!
Previously:
Update (2019-07-11): Jeff Nadeau:
A clever teardown, and not far off in principle
2 Comments RSS · Twitter
"the purpose here is to act as a cheat sheet or a place that you can pick up keywords"
I'd love to see something like this for AppKit, unfortunately, while SwiftUI is usable on iOS, there is still a very long read to go to make it useful on macOS.
For instance, there is currently no way to create a simple Master/Detail view, as the List component is not design to support selection, keyboard navigation, and all other behaviors that make it like a macOS component and not an iOS component.
"Should I learn SwiftUI?
Yes."
Not sure. SwiftUI currently looks like autolayout. And the story of autolayout did not end well.
