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

Get rid of Java in favor of Kotlin #177

Open
artem-zinnatullin opened this issue May 18, 2016 · 10 comments
Open

Get rid of Java in favor of Kotlin #177

artem-zinnatullin opened this issue May 18, 2016 · 10 comments
Assignees
Milestone

Comments

@artem-zinnatullin
Copy link
Owner

No description provided.

@artem-zinnatullin artem-zinnatullin added this to the v1.0 milestone May 18, 2016
@artem-zinnatullin artem-zinnatullin self-assigned this May 18, 2016
@williamwebb
Copy link

If this project is meant to showcase best practices for quality Android development i think it would be silly to replace the language that the vast majority of Android developers are using( not to mention is officially supported ). At least bases on my vastly uniformed understanding of current kotlin utilization levels now i believe it would vastly diminish the value of the project.

I am however fully in favor of having portions or even full sections being in kotlin.

@lenguyenthanh
Copy link
Contributor

I agree with @artem-zinnatullin, using Kotlin is one of the best practice for Android developers now. But we should keep Java as a separate branch.

I'd like to help you on this issue, Artem. Please tell me if I can help you anything.

@artem-zinnatullin
Copy link
Owner Author

Well, I definitely won't be able to support 2 versions of the app in different languages…

At least bases on my vastly uniformed understanding of current kotlin utilization levels now i believe it would vastly diminish the value of the project.

http://artemzin.com/blog/state-of-kotlin-as-main-language-for-android-project/

@lenguyenthanh thanks for suggesting your help, I'll ping you if something will be required besides code review!

@williamwebb
Copy link

I've read your article :). I meant utilization within the Android development community, not the viability of the language.

@artem-zinnatullin
Copy link
Owner Author

Well, quality of the code is part of quality matters :)

On Thu, May 19, 2016 at 6:15 PM, William Webb notifications@github.com
wrote:

I've read your article :). I meant utilization within the Android
development community, not the viability of the language.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#177 (comment)

@lenguyenthanh
Copy link
Contributor

@artem-zinnatullin always ready to help :). It's hard to convince people here to use Kotlin :(.

@danielgomezrico
Copy link
Contributor

@lenguyenthanh you can add kotlin by parts, I mean, kotlin is 100% interoperable with java, so you can have both files inside same project and compile them, use java from kotlin and kotlin from java, and have a low footprint inside the project because of Kotlin itself

@serj-lotutovici
Copy link
Contributor

You can also enable kotlin for functional and integration tests and then move to other parts of the app.

@adamint
Copy link

adamint commented Sep 28, 2017

Hey, say this was still open. Is this still wanted?

@artem-zinnatullin
Copy link
Owner Author

Yes

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

6 participants