|
|
|
|
|
by H_Romeu_Pinto
3311 days ago
|
|
The funniest part is how much this discussion sounds like the Java vs. Perl on web programming from decades ago. In the end it is just politics. What will make a framework or language succeed is how influential its sponsors are (e.g.: IBM -> Fortran & Cobol, ATT -> C, MS -> Basic & C#, Sun -> Java, Google -> Python, MS & ATT -> C++, Apple -> ObjectiveC). The ideological arguments are just decoration, fancy wrapping and cosmetics to convince people to buy the thing. If language "quality" alone was enough to win adepts, both Smalltalk and Lisp would be among the top 10 most used. Kotlin might be better than Java, in the same sense a Dvorak keyboard might be better than a qwerty. But it doesn't seem better enough to force old Java dogs to care for new tricks. Edit: typos. |
|
Don't count on that.
I'm an old dog when it comes to Java. But I decided to give Kotlin a try on a little pet project of mine.
JetBrains are mad geniuses. In Intellij, with a hotkey you can convert Java to Kotlin. A couple of Alt-Enters and you have something almost idiomatic.
I converted the entire (small) project in an hour and then spent a bunch of time reworking parts to take advantage of Kotlin's functional features.
And I could convert incrementally and test each migration because the Java interop is absolutely seamless. They've completely eliminated the risk and friction of trying the language out.
I even found a bug along the way due to Kotlin's null checker.
It's brilliant!
JetBrains gets it. They produced a language that's new yet familiar (sorry Clojure), powerful yet still easy to understand (sorry Scala), and has essentially zero barrier to entry due to interop and tooling support.