32 thoughts on “Java vs Kotlin for Android App Development

  1. Kotlin is another open-source programming language for present-day multi-stage applications that depends on the Java Virtual Machine (JVM). Strikingly, Kotlin is assigned as the official language of Android. The best thing is, it’s interoperable with existing Android languages. Besides, it very well may be effectively coordinated with Android Studio, which no other language offers, other than Java.

    Anyways, read the below. This might help.
    https://www.namasteui.com/why-kotlin-is-preferred-language-for-android-development/


    Regards,
    Sourav Basak
    Namaste UI

  2. @5:24 In Java, you never have to define constructors, getters and setters (uggh, please don't), hashcode(), toString(), or equals() if you don't need to. I've never once defined hashcode(). toString() maybe a dozen times, equals() even fewer….are you sure you've ever programmed in Java?

  3. how do null values "cause huge frustration for developers"? When I see a NullPointerException, I'm relieved; they're the easiest exception to deal with. Without them, I will have to 1) realize what's happening is not what's intended (which could take anywhere between seconds and months) 2) figure out why it's not doing what's intended 3) finally fix the boneheaded mistake. Debugging went from running once to potentially not even realizing there's a problem until well after launch.
    Null is one of the most powerful tools in a programmers pocket.
    Believe in the null.
    Trust in the null.

  4. Java was my second programming language, I learned oop on it in school, never really liked it over C++, started learning kotlin a few days ago and it looks to me like it is just Java but thinned with some python.

    I didn't develope an android app before, but I will now using Kotlin

  5. I'm making a Pathfinder 2e spell card app for my friends. I don't think it will take off, but it will be handy!

    Learning Kotlin is a bit tricky…hate learning new languages. I think in the long run I will be better off knowing it over Java though, even though I already know Java

  6. When I change the datatype of a function, I need to change the way the output is handled anyway so I don't see the point in not having to declare the datatype except not knowing what datatype something is and having bugs like in Javascript where 11+1 is 12 most of the time except when it's "111". Just my opinion on that matter

  7. As a professional mobile developer who has been developing iOS apps and been using Swift for like 6 years and have experience with Obj-C. Swift is much nicer. And I been doing some Android which I started with Java and Android as a side until about a year or so I been using Kotlin. I been taking Android seriously for over a year now and been using Kotlin. The way I see it is there will be plenty of legacy code out there so having familiarity with Obj-C and Java is a huge plus for that, but writing any new functionality or building any new apps I would use Swift for iOS and Kotlin for Android. I tend to avoid things like React Native as there is a whole slew of problems with it.

  8. well would say Java is a good language to know first it a good language so that you pick up new language easier maybe that why at college it the first programming language learned

  9. I just wanted to comment on the part where you said that Google may stop supporting Java, and I highly disagree. Most Android apps and parts of the OS itself since its inception are still written in Java and no one is seriously going to re-write all that code in Kotlin. That being said, Kotlin is interoperable with Java and you can write Java code in Kotlin, so you can write new apps in Kotlin, but as far as stop supporting Java, that won't happen in the near future.

    The same thing can be said with Objective-C. Parts of iOS and tons of apps since it's inception are still written in Objective-C and no one in Apple is going to re-write millions of lines of code in Swift just because it's a more modern language. Even many of the libraries and frameworks that iOS developers use is still written in Objective-C.

Leave a Reply

Your email address will not be published. Required fields are marked *