dont work(

https://github.com/square/leakcanary

dependencies {
   debugCompile 'com.squareup.leakcanary:leakcanary-android:1.5'
   releaseCompile 'com.squareup.leakcanary:leakcanary-android-no-op:1.5'
   testCompile 'com.squareup.leakcanary:leakcanary-android-no-op:1.5'
 }

You can of course use

()

and

GString

there.

this work for

groovy

build scripts, but not for

kotlin

scripts

Ohh. You are using Kotlin for gradle...

yee)

Then it's probably something gradle or Google has to implement. 🙂

No experience with that.

How does Android work? Do different apps get different instances of framework enums and all the other stuff?

@Paul Woitaschek each app runs its own sandboxed VM instance.

E. g. you can mutate

Build.SUPPORTED_ABIS

array, but this won’t affect other applications.

Any resources where I can read up on these internals?

Try Googling stuff about Zygote. It's where it all begins.

No surprise there.

@orangy you measure anko vs the layout inflater call?

It’s not me

@orangy has left the channel

Reflection is slower than direct method calls. Who knew

I ask myself if it matters or if it's the actual measurement that is costly

That would be a per-application thing to check

Curious how the measurements were taken

The only way to get real perf numbers is systrace and ensuring the CPUs are running at full frequency and not in a low-power mode

I'm betting this person did currentTimeMillis subtraction in a loop which isn't exactly scientific

Also, I have a strong hope that Anko will make removing unused parts of AppCompat with ProGuard easier...

@mg6maciej I've used Anko in a couple of production apps. And I've switched back to xml because I ran in some weird styling issues.

@miha-x64 Could you share the most complex layout you have created with Anko? Did you hit any wall and had to go back to xml for any reason? 2 replies I've shared some of my Anko code. Don't remember whether it was in #anko or in #codingconventions, both have been lost in Slack history 🙂 I have no complex layouts. 🙃 While using Anko DSL, I typically prefer two-space indentation to fit lines easier. I also set adapters, decorations and all these things in Fragment's onCreateView. Adapters are typically represented by anonymous classes and contain item views, so all fragment's UI is quite monolithic and declared in a single place.

@saryong has left the channel