3 ms·

Flutter guys explained why Dart: at the time they were making decision they looked at bunch of languages and Dart came at the top. At the time Kotlin either did

by kjksf 9y ago

Flutter guys explained why Dart: at the time they were making decision they looked at bunch of languages and Dart came at the top. At the time Kotlin either didn't exist or was at extremely early stages. Regardless of history, Kotlin is, in the end, a JVM language. If you want to ship a Kotlin app, you need to ship JVM. Getting JVM to a reasonable size is a great technical challenge not to mention Oracle made it clear what they think about other companies reimplementing "their" APIs. (I do know about Kotlin Native but that's far, far future). Also, Google is not a Borg or centrally planned economy with 5 year plan. Flutter happened because a bunch of Chrome devs wanted to experiment with a better way to write mobile apps, not because Larry dictated that "Flutter is now long term strategic investment, so go and do it". Flutter happened to be a promising technology so it's getting increased attention and funding. But it could just as well fail, like AtScript did.

k__ 9y ago
Hu? I thought the JVM isn't an issue on Android, becaue it's ingrained in the OS itself. (Dalvik/ART)
- jayd16 9y ago
  Its not but Flutter is meant to be a cross platform solution.
kodablah 9y ago
> I do know about Kotlin Native but that's far, far future If you mean adoption, sure, but from using it a good bit lately, I'd say the tech is basically there.
sandGorgon 9y ago
Kotlin Native is not far - the repo already has a lot of sample apps that you can run today. https://github.com/JetBrains/kotlin-native/tree/master/samples https://github.com/JetBrains/kotlin-native/tree/master/sampl... KotlinConf app in ios was in production release on Kotlin/Native - https://github.com/JetBrains/kotlinconf-app https://github.com/JetBrains/kotlinconf-app -> https://itunes.apple.com/us/app/kotlinconf/id1299196584?mt=8 https://itunes.apple.com/us/app/kotlinconf/id1299196584?mt=8 Do note that this is without the weight of Google's support behind it. I'm not quite sure why you say its far-far in the future. Given Flutter's own maturity, I dont see them being very differently placed in terms of production readiness - https://flutter.io/faq/#should-i-build-my-next-production-app-with-flutter https://flutter.io/faq/#should-i-build-my-next-production-ap... Kotlin is a perfect bridge - works brilliantly on the JVM, works brilliantly natively, everyone loves it, simple migration path from Android -> Fuchsia

by kjksf 9y ago

k__ 9y ago

Hu? I thought the JVM isn't an issue on Android, becaue it's ingrained in the OS itself. (Dalvik/ART)

jayd16 9y ago
Its not but Flutter is meant to be a cross platform solution.

kodablah 9y ago

> I do know about Kotlin Native but that's far, far future If you mean adoption, sure, but from using it a good bit lately, I'd say the tech is basically there.

sandGorgon 9y ago

Kotlin Native is not far - the repo already has a lot of sample apps that you can run today. https://github.com/JetBrains/kotlin-native/tree/master/samples https://github.com/JetBrains/kotlin-native/tree/master/sampl... KotlinConf app in ios was in production release on Kotlin/Native - https://github.com/JetBrains/kotlinconf-app https://github.com/JetBrains/kotlinconf-app -> https://itunes.apple.com/us/app/kotlinconf/id1299196584?mt=8 https://itunes.apple.com/us/app/kotlinconf/id1299196584?mt=8 Do note that this is without the weight of Google's support behind it. I'm not quite sure why you say its far-far in the future. Given Flutter's own maturity, I dont see them being very differently placed in terms of production readiness - https://flutter.io/faq/#should-i-build-my-next-production-app-with-flutter https://flutter.io/faq/#should-i-build-my-next-production-ap... Kotlin is a perfect bridge - works brilliantly on the JVM, works brilliantly natively, everyone loves it, simple migration path from Android -> Fuchsia