Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Swift? #69

Closed
calmh opened this issue Jul 28, 2018 · 2 comments
Closed

Allow Swift? #69

calmh opened this issue Jul 28, 2018 · 2 comments

Comments

@calmh
Copy link
Member

calmh commented Jul 28, 2018

Discussion point: should it be acceptable to add new code/classes as Swift, and/or refactor existing ones into Swift? I personally have a slight preference for Swift and think that's the direction the environment is moving in. I'm also OK with Objective-C if that's where we want to remain for good reasons.

@calmh calmh changed the title Allow Swift Allow Swift? Jul 28, 2018
@calmh calmh added the question label Jul 28, 2018
@xor-gate
Copy link
Member

Actually I did read today about the differences in Swift and if it is wise to switch. I don't mind to much learning Swift and gradual rewrite it. I found a nice article https://www.hackingwithswift.com/articles/27/why-many-developers-still-prefer-objective-c-to-swift. And some apple recommendations: https://developer.apple.com/documentation/swift/migrating_your_objective_c_code_to_swift. I agree with some points about Objective-C, but as the project is small and will not become a big one as it is just a simple wrapper we should move in the more maintainable and contribution friendly direction.

@calmh
Copy link
Member Author

calmh commented Jul 29, 2018

Answered

@calmh calmh closed this as completed Jul 29, 2018
@syncthing syncthing locked and limited conversation to collaborators Jul 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants