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

Is there a reason for using Swift? #32

Closed
long1eu opened this issue Mar 5, 2019 · 5 comments
Closed

Is there a reason for using Swift? #32

long1eu opened this issue Mar 5, 2019 · 5 comments

Comments

@long1eu
Copy link

long1eu commented Mar 5, 2019

flutter/flutter#17999 (comment)

@tobrun
Copy link
Collaborator

tobrun commented Mar 6, 2019

Thank you for highlighting @long1eu!

cc @andrea689

@andrea689
Copy link
Collaborator

@long1eu I used Swift because I don't know ObjectiveC very well. I didn't know about this Swift overhead!

@tobrun tobrun added this to the future milestone Mar 9, 2019
@tobrun
Copy link
Collaborator

tobrun commented Mar 9, 2019

This is a nice to have in the long run, since the code base isn't that large it shouldn't be too much work. Adding this to the future milestone as the focus now lies into releasing a v0.0.2 version of the plugin.

@andrea689
Copy link
Collaborator

andrea689 commented Mar 10, 2019

I have do many researches, and I found that this size increment is due to Swift standard library and runtime that are included in every app, but with the release of Swift 5.0 this year, these libraries will be available by OS and the app size will not be affected.
Swift is the successor of ObjectiveC that will replace it in the long time, so I think that is better to keep the plugin in Swift.
Reference 1: Swift 5 Primary Focus: ABI Stability
Reference 2: What Does ABI Stability Enable?

@tobrun tobrun closed this as completed Nov 10, 2019
@long1eu
Copy link
Author

long1eu commented Nov 10, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants