Well in case FP people forgot a lot of things they use are built with OOP style.
And it's worse on global scale now FP vs OOP. Just hate the Java all the way and compare previous issues with current features of opposite program. Take for example C# it's like Kotlin guys. It's too much this vs that in software and it's only getting worse lately. Readability is subjective and any statistics on productivity should be based on facts. Shorter lines of code (especially when not significant) do not guarantee the project would be delivered faster. We should also focus on getting the job done and maintainable. If you wrote it with Flutter, marvellous! If you wrote it using React native, wonderful! If you wrote the app using C++ and it works fine as expected, great! If you are using Java on Android, Awesome!Īlso check out RxJava for Android Developers. In the end, the users/clients might not even know or care about what an If Statement means. If you want to read a great article on why Kotlin does not instantly mean readability and productivity read this article.Īdopting Kotlin does not guarantee you would have happier developers, fewer bugs and skyrocketing profit. The common arguments I hear are readability and productivity. If you would like to know more about Kotlin check out the Kotlin in Action ebook.īut being a fan of one language shouldn’t make you an enemy of another. It is possible to see Java 12 code and mistakenly think it is Kotlin, that's how much Java has improved. If you have noticed, I haven't spoken of the current Java 12 features. If you are familiar with Android development you would know that in order to use Java Streams, which was a feature in Java 8 (2014), you would need to be on API level 24 or higher to use it on Android.įor clarity sake, API level 24 is Android Nougat.Īnother Java 8 feature ( which you can now access on Android) is CompletableFutures which could replace all the lines of your AsyncTask Class with just a few lines of code. Java 8 features are now being added to Android for developers to make use of. The Java used on Android is mainly Java 7 and a little of Java 8. In case you are not aware, the latest Java version is Java 12. When people compare Kotlin with Java they, sometimes unknowingly, are comparing Kotlin with Java 7. If a tool is solid and stands the test of time, people would adopt it.Īnother mistake I see is when people compare Kotlin's current features with Java's past issues. I use both Java and Kotlin and can say that Kotlin is a wonderful language.īut here is the issue, to uplift a language, you do not need to talk down on another. In the Android community, there is this constant battle of Java and Kotlin which, in my opinion, is very unnecessary. I went on to check out the Reddit Post spoken of.
0 kommentar(er)
