johnwick17

3 ms·

1. 1.▲
   by johnwick17 8y ago

   I have seen his other posts and he is a smart guy. No idea what bit him with Kotlin though...
2. 2.▲
   by johnwick17 8y ago

   Maybe it is just me but when I critique things then I make sure that I am 100% right. This article, in its current form, can do a lot of harm for people who will read it and decide not to try Kotlin because author has had some problems with
3. 3.▲
   by johnwick17 8y ago

   Ok I have overstepped a bit (edited the post), but I will stick to the "did not bother" and "no clue". Documentation for Kotlin is really nice and it is there together with amazing Kotlin Koans online. Do you think that
4. 4.▲
   by johnwick17 8y ago

   Now that I look at the article, it occurred to me that author might have already been biased when trying Kotlin out and was already certain about the outcome hence the rather poor argumentation. The article itself is rather poorly organized
5. 5.▲
   by johnwick17 8y ago

   My 5 cents: It seems to me that the author did not spent enough time to learn Kotlin. The way he mixes Java types (Integer.parseInt) inside pure Kotlin code and then complains about lack of Null-Safety? It is enough to use an extension func