Android KTX: Kotlin Development for Android

#1

Post by ingve » Mon, Feb 05, 2018, 8:35 PM UTC

Android KTX: Kotlin Development for Android
android-developers.googleblog.com

Re: Android KTX: Kotlin Development for Android

#2

Post by bitwize » Mon, Feb 05, 2018, 8:54 PM UTC

Still working in Java on Android. Have a feeling that I will be left behind soon.

Re: Android KTX: Kotlin Development for Android

#3

Post by saagarjha » Mon, Feb 05, 2018, 9:01 PM UTC

We've already seen something similar before: when Apple "modernized" many of the their Cocoa Touch APIs to work better with Swift.

Re: Android KTX: Kotlin Development for Android

#4

Post by merb » Mon, Feb 05, 2018, 9:05 PM UTC

some examples are fine, but come on...

> Uri.parse(myUriString)

vs.

> myUriString.toUri()

I'm not sure if I would prefer the second one...

Re: Android KTX: Kotlin Development for Android

#5

Post by wootie512 » Mon, Feb 05, 2018, 9:06 PM UTC

bitwize wrote: post #2

Still working in Java on Android. Have a feeling that I will be left behind soon.

Same here. On my my most recent project the client requested we use Java, since after they take over they can use devs with Java knowledge.

Re: Android KTX: Kotlin Development for Android

#6

Post by evancox100 » Mon, Feb 05, 2018, 9:07 PM UTC

Why is it that these large web companies can put out such sophisticated tools, and yet can't make a functional web page? Literally cannot see the content you are trying to show me.

https://imgur.com/a/lXY8J

And no, there's no scrolling or zooming allowed.

Seriously, let's stop the focus on web framework du jour and actually make web sites that work, please.

Re: Android KTX: Kotlin Development for Android

#7

Post by kornish » Mon, Feb 05, 2018, 9:07 PM UTC

merb wrote: post #4

some examples are fine, but come on... > Uri.parse(myUriString) vs. > myUriString.toUri() I'm not sure if I would prefer the second one...

Discoverability via autocomplete is much higher in the second one. Extension methods probably seem really strange to anyone coming from a FP background (myself included), but in practice they've ended up being pretty useful when paired with Intellij.

Re: Android KTX: Kotlin Development for Android

#8

Post by TheAceOfHearts » Mon, Feb 05, 2018, 9:09 PM UTC

merb wrote: post #4

some examples are fine, but come on... > Uri.parse(myUriString) vs. > myUriString.toUri() I'm not sure if I would prefer the second one...

I was about to post the same thing. The first one makes way more sense to me.

Re: Android KTX: Kotlin Development for Android

#9

Post by TheAceOfHearts » Mon, Feb 05, 2018, 9:12 PM UTC

kornish wrote: post #7

merb wrote: post #4

some examples are fine, but come on... > Uri.parse(myUriString) vs. > myUriString.toUri() I'm not sure if I would prefer the second one...

Discoverability via autocomplete is much higher in the second one. Extension methods probably seem really strange to anyone coming from a FP background (myself included), but in practice they've ended up being pretty useful when paired with Intellij.

Doesn't it get a bit overwhelming to get a huge list of choices with autocomplete? I've never done any serious work with Java or Kotlin, so I'm genuinely curious.

As long as you have good docs, I find discoverability is rarely an issue. One of the first things I do when picking up a language is look through its built-in constructs, to familiarize myself with the available options.

Re: Android KTX: Kotlin Development for Android

#10

Post by Techonomicon » Mon, Feb 05, 2018, 9:14 PM UTC

saagarjha wrote: post #3

We've already seen something similar before: when Apple "modernized" many of the their Cocoa Touch APIs to work better with Swift.

What does "already seeing this" have to do with any meaningful input on the subject?