In order to vote, comment or post rants, you need to confirm your email address.
You should have received a welcome email with a confirm link when you signed up. If you can't find the email, click the button below.

!rant

Goodbye Java I will not miss you at all! I swear ...

I do like it when making web services (especially that I can use Java8) but for Android you have been a torture. Hello sweet Kotlin! I shall embrace you and treat you like my newly born baby!!

Story is:
Working on a new project where I need to talk to a web service (also made by me).
Started writing in Java, all is cool and unit tests pass.
Downloaded Android Studio 3 Beta 1 and converted my Java code to Kotlin, That AsyncTask did not look nice in kotlin, converted it to async & await feature and I must admit lots of code removed, no more need to create a new fucking AsyncTask every time the app sneezes for data!

I feel like I'm working with C# but with difference in syntax.
My life is now complete :)

I mean it is a much easier decision than switching the entire team over to using Kotlin exclusively. You could just use it on new files or where existing files need rewrites. There is no need to replace existing Java files.

It is much easier to integrate in to existing projects than say, Swift in to Obj-C as you can just add the .kt file and away it goes (with appropriate dependency and gradle)

@xsacha Looks great for new files though, I might try that as well, new files will begin as small ones and I suppose it is fair enough to assume team will be able to start adapting to Kotlin with new small files. Thanks for you suggestion :)