Repository navigation
Replies: 2 comments
|
@beqabeqa473 do you have an opinion on this? Or would you rather spend your efforts on converting to Flutter? |
0 replies
|
Personally I would advise heavily against moving to flutter. It is well known in the blind community for making hardly usable and inefficient apps. It doesn't have custom actions support, semantics on non mobile platforms basically don't exist, etc. Of course, this isn't my choice, but just my opinion |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
A question before anyone writes code, not a proposal.
Client/TeamTalkAndroid/build.gradlesetsenableKotlin = false, added in #3057 when the build was modernized. So the module is Java only today, on purpose or by default.Would you accept Kotlin sources in TeamTalkAndroid?
Points either way, as I see them:
Library/TeamTalkJNIand stay Java, so any conversion is partial by definition and the module would hold two languages for a long time.MainActivity.java(2,500 lines), where null handling and boilerplate cost real review time.If the answer is no, that is a fine answer and worth writing down so it stops coming up. If the answer is yes, I would suggest a rule up front: new files may be Kotlin, existing files are converted only one per PR and only when they are being touched anyway.
Application
All reactions