Android Now Supports the Kotlin Programming Language (venturebeat.com)
In addition to Java and C++, Google announced at its I/O 2017 conference today that Android is gaining official support for the Kotlin programming language. VentureBeat reports: Kotlin is developed by JetBrains, the same people who created IntelliJ. Google describes Kotlin, which is an open sourced project under the Apache 2.0 license, as "a brilliantly designed, mature language that we believe will make Android development faster and more fun." The company notes that some have already adopted the programming language for their production apps, including Expedia, Flipboard, Pinterest, and Square. There are already many enthusiastic Kotlin developers for Android, and the company says it is simply listening to what the community wants. But Google's choice didn't just come down to the team believing Kotlin will make writing Android apps easier. Developers will be happy to know that Kotlin's compiler emits Java byte-code. Kotlin can call Java, and Java can call Kotlin. Indeed, "the effortless interoperation between the two languages" was a large part of Kotlin's appeal to the Android team. This means you can add as little or as much Kotlin into your existing codebase as you want, mixing the two languages freely within the same project. Calling out to Kotlin code from Java code should just work, while calling to Java code requires some automatically applied translation conventions.
New week, new language-of-the-week.
Fucking millennials can't use languages that have worked for decades because "it's old".
Idiots.
NEXT!
Literally *none* of what you spewed here is true.
This looks an awful lot like ruby. Can someone show me the differences?
I'll never heard of this new flavor of the week. But I had heard of Jetbrains. I use PyCharm IDE every day.
Or relevant, since the article is about a language that is not Java running on a platform (Android) that doesn't use the Java Virtual Machine (or any virtual machine, for that matter, since Android uses ahead of time compilation to generate native executables).
I've been using Kotlin for Android development for a while now. It's not a passing fad, and it may one day overtake Java in many things. It's just Java with additional desperately needed features.
I've heard no one whine about Swift being the flavor of the week, and yet, if you compare the languages, they are almost the same language with some slight syntactic differences. Both have null-safe typing. Both have lambdas quickly accessible. Both have extension functions. Both have interfaces that can contain default implementations. Both have getters/setters.
The only difference is that Swift was basically forced upon the iOS world, while Kotlin had to earn its place.
So I click the first link "concise" and it shows me how to make a singleton. I thought singletons have basically been declared to be an anti-pattern. They're basically a name for an obfusticated global and make testing difficult.
Not very inspiring to see a bad example as the first introduction to the language. It doesn't give much confidence that the team making the language actually gets bets practices.
Come on corporate overlords, you are swimming in money. Pay the fee and give us real Java with the full library.
Heard of that one google? It's quite popular. How about supporting that instead of this thing which will go nowhere and be dropped in a few years?
I'm waiting a lexer/parser generator for Kotlin similar to JFlex/CUP.
"a brilliantly designed, mature language"
I have no reason to be suspect of the first part of that statement, but "mature"? Come on.
Is it just me, or do you all find the recent move to platform-specific languages very worrying indeed? So for anything MS-like we're supposed to be C#, on xOS the new hotness is Swift, and on Android, it's Kotlin (or Go? or Java?).
What's worse is that the only really cross-platform language remains C (there's plenty of real platforms with marginal C++, iOS for instance) and even that's easy to use only within Obj-C, which we're not supposed to like anymore.
Fantastic, thanks, large natural monopolies.
I find it ironic that the people (Android team engineers) that don't want to use Java enums on Android APIs because they add "bloat" are embracing another language that adds more overhead over plain Java (increased application size for example) than enums could add.
Get to a decision, why are you also making dart and go.
You type too much.
Python is the first mistake.
Actually, he's 100% correct on all points, Mr Java apologist.