it changed to enabled after update

strange

oh

will try building without it

try disabling, I'm pretty sure it is the IR processing throwing off the dexer

I petty sure I had it disabled

hmm, the RC could've imported the 1.5 settings though?

afaik the RC versions use a different settings folder from the preview versions

yes, most likely that's the reason

@damianpetla: I’m sorry, didn’t describe it well. I wanted to know if there is some good/bad experience after migration to Kotlin, specially for adapters with data classes. Something like pros/cons or so. Sorry again

For me there are pros only

Good evening people. Maybe this question is coming up all the time, but is there any up to date good tutorials how to get started with android prog? And not just "This is how you install it and convert the mainView to kotlin"

or what are the best tutorials , written/video, I can follow? :)

@troligtvis: the best way to start programming android apps is to start with java. And I believe google have a complete tutorials for that http://developer.android.com/about/start.html

@troligtvis As Denis says, your best bet is to follow the official tutorials from Google. Commonsware.com and Vogella.com are good sources too, and of course StackOverflow is your friend. To start off you should probably focus on learning about Android itself in the official language for which there are the most resources out there, and switching from Java to Kotlin later when you have at least the basics down should be a breeze. Not to mention, you'll appreciate Kotlin all the more for it later :)

Thanks @defuera @matej. Yeah it seems the way to go, learn android dev with java then translate it to kotlin. I know java so it wont be a problem and I’m currently an iOS dev so I’m running with Swift which Kotlin is very similar to. :)

I know it's hard to stick with Java when you know there's something so much better available, but after a few weeks of diving deep into Android with Java you should be ready to start looking at Kotlin. If Google endorsed Kotlin as an official language for the platform, and provided code samples for it the way that Apple does for Swift, I think we'd all wholehartedly recommend that you go straight to Kotlin. Sadly that's just not the case.

Mh let’s hope Google will endorse Kotlin :)

That would be amazing, but it feels like they're apprehensive. When you think about it, it would make total sense, given their investment in the JVM, great integration with the tools, the fantastic Java interop in Kotlin, and the developer mind share it's gaining in the Android dev community. I think all it really needs is for us to keep vocally expressing how much we prefer Kotlin over Java, for the JB guys to continue their excellent work and at some point it won't be possible for Google to deny that the people have spoken. Kotlin got me excited about Android development again and I think it's safe to say the same is true for most people who've tried it.

Yeah it would be great! Hopefully this will happen :)

@matej: absolutely agree. We didn’t sell IntelliJ to Google one day over golf to build Android Studio, it were people who preferred IJ to Eclipse, and they were telling this a lot of times, in various places. Google listens, as far as I can tell, but doesn’t tell it’s listening. Then it just moves simple smile

It's a delicate position. Whatever they say about Kotlin (or any technology they don't directly control) will immediately be understood as "fully supported", which means they will start getting feature requests, bug reports, etc...

The best approach right now is to remain silent but behind the covers, do their best to accomodate Kotlin. Just never acknowledge it.

@cedric Well, let's not hope that they 'never' aknowledge it :) But you are right about them having to be careful regarding what they endorse. Considering Android is such a large component of Google's product portfolio, it's not hard to understand why they would be cautious until they're absolutely certain that Kotlin is really taking off like a rocket ship. With the perfect storm of mature tooling, a competent and dedicated team working on it, seamless integration with the existing framework and libraries, plus the embrace of more and more devs, it certainly looks like it's on the right path to do just that, so fingers crossed!

Just to add another perspective: does anyone else fear that Android is becoming the platform for the stupid people? Google’s videos are offensivley idiotic with people making faces and bugging out their eyes constantly, the Dev Summit, while a good thing overall, the sessions were good, had the feeling of gathering the children around. The session on testing essentially said ‘we’ve seen the code you jokers are writing and its a disaster.’ Go imagine one of those googly-eyed videos trying to tell people about Kotlin and see if just a little cognitive dissonance doesn’t result.

@codeslubber its true though, the Android eco system is filled with bad code, bad architecture and so on - just look at stackoverflow. In my opinion that's Google's own fault as the Android framework makes it easy to write messy, strongly coupled code. It would be even worse without the efforts of community members like the square guys. Google finally acknowledged that and is trying to promote best practices and good architecture (with varying results)

@kirillrakhman: oh believe me I am not doubting that for one minute, nor saying Google is wrong, and I think what they are doing with tests is great, the overall testing grade in the latest rev is much higher I think: JU4 tests finally, Espresso is decent, and they run much faster thanks to JB… just saying when stupid runs free for a long time, bread and circus takes over then we’re all doomed...

I think we also agree about the fact that G did leave the door open to really poor code.. android clearly was a project that did not spend a long time on the conceptual phase (necessity doomed that) so yeah there are not strong patterns in part because at first it all just seems pretty random: Intents/Actions/Context.. I found that my respect for android grew as I used it more and did more with Services.. I make a somewhat perverse argument that the microservice, must learn concurrency guys piling up like cord wood in the server space should go look at android, it did microservices a while ago, and did them well...

Well, we designed most of these API's in 2007, the state of the art in software was very different. At least, Android is flexible enough to embrace newer styles of programming (DI, annotation processors, new languages, RecyclerView, loaders, etc...) reasonably gracefully.

I'd also caution about the attitude that most developers are stupid. I don't think the Android population is any different from any other massively successful technological stack. It's a bell curve, there's a bit of everything.