You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.
Each PropertyCross implementation should show what we believe to be the most effective way of using each framework.
Therefore, I would like to ask whether we, as a community, think that Swift (version 2.0) is the most effective way of doing "native" iOS development for PropertyCross or whether we should stick with Objective-C for the moment?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In a separate issue (#282), @ColinEberhardt raised an interesting point:
Therefore, I would like to ask whether we, as a community, think that Swift (version 2.0) is the most effective way of doing "native" iOS development for PropertyCross or whether we should stick with Objective-C for the moment?
The text was updated successfully, but these errors were encountered: