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 witch the plugin is written using Swift? #178

Closed
long1eu opened this issue Feb 5, 2019 · 4 comments
Closed

Is there a reason for witch the plugin is written using Swift? #178

long1eu opened this issue Feb 5, 2019 · 4 comments

Comments

@long1eu
Copy link

long1eu commented Feb 5, 2019

flutter/flutter#17999

@mvanbeusekom
Copy link
Member

The main reason is that we don't (want to) understand Objective-C and because it is the recommended language by Apple (quoted from here):

Swift is a successor to both the C and Objective-C languages. It includes low-level primitives such as types, flow control, and operators. It also provides object-oriented features such as classes, protocols, and generics, giving Cocoa and Cocoa Touch developers the performance and power they demand.

Unfortunately when we started developing we didn't realize (like so many of us) that using Swift and Flutter would have such a big penalty in the final app size. Now we are so far in that we don't have the knowledge or time to translate the plugins (see also permission_handler) back to Objective-C.

@long1eu
Copy link
Author

long1eu commented Feb 13, 2019 via email

@mvanbeusekom
Copy link
Member

Yes we definitely do, if you would also be willing to take the permission_handler into account.

@long1eu
Copy link
Author

long1eu commented Feb 13, 2019 via email

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

No branches or pull requests

2 participants