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

Kotlin #3

Closed
Doomsdayrs opened this issue Apr 13, 2022 · 5 comments
Closed

Kotlin #3

Doomsdayrs opened this issue Apr 13, 2022 · 5 comments

Comments

@Doomsdayrs
Copy link

The android ecosystem is moving towards using Kotlin.

Using Java will inhibit the future maintainability of the application.

Consider converting to Kotlin overtime.

@grishka
Copy link
Member

grishka commented Apr 13, 2022

Consider converting to Kotlin overtime.

To solve what?

@grishka grishka closed this as completed Apr 13, 2022
@Doomsdayrs
Copy link
Author

Java is not the language for Android anymore. Its easier to develop new features in Kotlin.

Kotlin has less overhead and is more maintainable.

@grishka
Copy link
Member

grishka commented Apr 13, 2022

Java is not the language for Android anymore.

Because Google says so? The same Google who can never make up its mind and settle for something that gets the job done? The same Google that comes out with ever more, ever more nonsensical abstractions on top of Android that solve all those problems no one has ever had?

Its easier to develop new features in Kotlin.

For me it's easier to develop new features in a language that I've been using for more than a decade, that doesn't try to outsmart me, that I don't have to fight, and that isn't a moving target.

Kotlin has less overhead and is more maintainable.

This is subjective. Are you trying to tell me that there are developers who know Kotlin but don't know Java? Shame on them then.

@Doomsdayrs
Copy link
Author

Because Google says so? The same Google who can never make up its mind and settle for something that gets the job done? The same Google that comes out with ever more, ever more nonsensical abstractions on top of Android that solve all those problems no one has ever had?

While you might have some previous dislike for Googles actions in certain departments. And that you have something you are comfortable with. I don't see how that relates to the very large and growing Kotlin developer scene.

For me it's easier to develop new features in a language that I've been using for more than a decade, that doesn't try to outsmart me, that I don't have to fight, and that isn't a moving target.

I can understand that Java is something you are comfortable with, but is it the best choice going forward when Google is trying to move onto Kotlin, and new developers in the now and future will be using Kotlin more and more.

This is subjective. Are you trying to tell me that there are developers who know Kotlin but don't know Java? Shame on them then.

Nearly all computer programmers are taught Java, but that does not mean they all like coding in Java. Neither does it mean they have proficiency in coding in Java, nor does it mean they even have the capability to properly digest Java codebases.

Please do consider that Kotlin is easier to write, it requires less to type and is simpler on the eyes. While Java has its history, Kotlin has versatility that you don't have in Java.

@Gargron
Copy link
Member

Gargron commented Apr 13, 2022

I’m sorry but I don’t see the point in allowing this discussion to continue. Our programming language choice is ours to make and there’s nothing wrong with using Java for Android apps at the moment.

@mastodon mastodon locked as too heated and limited conversation to collaborators Apr 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants