Google's Journey from Java to Kotlin for Server Side Programming by James Ward , Brad Hawkes , John

Поділитися
Вставка
  • Опубліковано 12 жов 2022
  • Kotlin is now a recommended programming language for server-side JVM usage at Google, while still providing access to a large existing Java ecosystem. With over 11 million lines of Kotlin code at Google (across server and Android), we've done a number of things to ensure our developers are successful with Kotlin. This talk will explore the challenges we faced, and the reasons we're adding Kotlin as an available language and how we've made it a successful change.
  • Наука та технологія

КОМЕНТАРІ • 34

  • @elliotbarlas
    @elliotbarlas Рік тому +57

    Congratulations to the Kotlin team at Google. But there was absolutely no mention of Kotlin being the server JVM language of choice at Google going forward or Kotlin replacing Java. The description is oddly misleading.

    • @TimSchraepen
      @TimSchraepen Рік тому +4

      Weirdly, I didn’t seem to have made that assumption.
      What I did hear them say is that they’re leaving it up to the teams themselves to decide whether to pick up Kotlin or not. I can only assume they’ve got some internal marketing going on, but I’d be interested to see which it is exactly.

    • @elliotbarlas
      @elliotbarlas Рік тому +5

      @@TimSchraepen what assumption? I'm comparing the language in the video description to the video content. They don't match.

    • @kevinb9n
      @kevinb9n Рік тому +1

      Strangely, that description has been completely revised now! The new description is *much* more accurate / supported by the talk itself.

    • @JamesWard
      @JamesWard Рік тому +1

      Some teams are choosing to replace Java with Kotlin but it is not mandated and in many teams Kotlin & Java live happily together. The previous talk description was ambiguous so we've updated it.

    • @cassiodias1965
      @cassiodias1965 Рік тому

      Is google using Golang for server side James? Thx for the video!

  • @Soulcybering
    @Soulcybering Рік тому +1

    Thank you very much for this talk. Really informative. 👍

  • @2pi1966
    @2pi1966 Рік тому +3

    Blown away, thank you for (yet) another great talk on Kotlin James, Brad and John! Will definitely share these findings with my colleagues.

  • @rosscousens6263
    @rosscousens6263 9 місяців тому +1

    Loom is here, baby! Less than a year!

  • @sidkolhapure94
    @sidkolhapure94 Рік тому +4

    Yeah I like using Kotlin at Amazon for server side programming.

  • @serhat0099
    @serhat0099 Рік тому +3

    so if the server framework isn't spring, but it's like spring, what exactly is it? why are they making a secret of it?

    • @mcunacom1328
      @mcunacom1328 4 місяці тому

      he said that they use GUICE. no secret :)

  • @guillemgarcia3630
    @guillemgarcia3630 Рік тому +2

    Why not golang for servers instead of kotlin? It is strange that a language made by google for web backends is not as used as kotlin. Is it purely for java interop?

    • @JaeTLDR1
      @JaeTLDR1 Рік тому +5

      . Infrastructure is already built around the jvm and the code base is in Java Kotlin. It is extremely expensive to rewrite apps on that scale
      Google uses go python and cpp elsewhere in other apps but this is only talking about the jvm apps

    • @cassiodias1965
      @cassiodias1965 Рік тому +1

      But is it ok to create new server-side apps using Go?

  • @spyro440
    @spyro440 Рік тому +3

    So, does Google now prefer Kotlin over Java for their backend services internally? Are developers encouraged to start new projects in Kotlin?

    • @mr.invisible5528
      @mr.invisible5528 Рік тому +10

      I cannot understand why people would choose java over kotlin for new projects. Why walk when you can fly?

    • @RomanTchekashov
      @RomanTchekashov Рік тому +5

      ​@@mr.invisible5528 because Java already have and getting more features which Kotlin has. Just use new versions if you want. If you already experienced Java developer you already know a lot what is underhood and how to tune everything for better performance. You mostly thinking about business logic and not about how to do it in new language and what to expect from it. If you need syntactic sugar just use new versions of Java. You should think about VALUE which you produce! If you new developer you can take any language you want but if you experienced one then you should think about a lot of things and definitely should not just follow the HYPE.

    • @jackdanyal4329
      @jackdanyal4329 Рік тому +2

      @@mr.invisible5528 actually even with kotlin you need java and will need in future. a lot of libs are written on java :)

    • @akin242002
      @akin242002 Рік тому +1

      @@RomanTchekashov For those resistant to change, there is a Java to Kotlin converter. Just write it in Java and convert it to Kotlin.

    • @RomanTchekashov
      @RomanTchekashov Рік тому +2

      @@akin242002 What’s the point to do that?

  • @radhekishansoni8381
    @radhekishansoni8381 Рік тому +3

    Didn't they choose it to avoid conflict with Oracle?

    • @tomchandler2356
      @tomchandler2356 Рік тому +1

      Yeah, but Oracle lost the lawsuit and Google + Jetbrains invested a lot in the language so now they have to market it somehow.

    • @yeeteshpulstya9890
      @yeeteshpulstya9890 Місяць тому

      But the language is actually good with null safety and less verbosity as compared to java

  • @sevenlabs2733
    @sevenlabs2733 Рік тому

    HI; i need some help. how i can get gender and birthdate form google account using kotlin??

  • @zolongOne
    @zolongOne Рік тому

    "Kotlin? what's that?" I want to meet this person 😂

  • @Luix
    @Luix Рік тому +1

    kotlin Go and the other C alternative…

  • @kenyee88
    @kenyee88 Рік тому

    AndroidLint is a pig to use on Android... Surprised you're not using Detekt instead on the backend code...

  • @akin242002
    @akin242002 Рік тому +1

    I love that Google is pushing for Kotlin and Go on the server side. I know it was a challenge to get around old Java legacy code, but with the Kotlin converter that isn't an issue anymore. Bye bye Java!