One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
Kotlin for me, but I am biased since I learned Java with Android, which makes it look extra bad.
I wonder why Google has this wait and see attitude instead of just ensuring that there is 1 best way to do all of these things...
I am not surprised, whenever they recommended one way to do things, they choosed the worst option: multiple activities, fragments, loaders, async tasks, ....
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
This sucks a lot.
I will launch a project in the coming week in the hope to make the transition easier.
Avoid any recommendations from Google and do whatever makes sense in your particular context.
Use callbacks, that's the universal idiom and they can be converted to coroutines in a few lines.
Callbacks and Kotlin Flows - Roman Elizarov - Medium
Roman Elizarov γ» 5 min read
Kotlin for me, but I am biased since I learned Java with Android, which makes it look extra bad.
I am not surprised, whenever they recommended one way to do things, they choosed the worst option: multiple activities, fragments, loaders, async tasks, ....
Yeah, will probably do something like this to make it work well for everyone:
github.com/square/retrofit/tree/ma...
I am curious about your thoughts on the AndroidX vs Support libraries mess and how it affects you as a library author.