I absolutely agree with you, Alan! The question is not only still remains open, but now (due introduction the room-library) becomes even more controversial. I'd like to see a united logic of interaction between all parts AOSP(especially framework's API)
*ContentProvider's -> Cursors -> CursorLoaders -> CursorAdapters* seemed like a good start to consistency, but a bit raw. *So today it still looks undeveloped, and the "room" is still young(moreover, it is not a substitute: there is no support for IPC, memory efficiency), the cursor-philosophy is also not declared deprecated. ((* -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/51260461-de4b-41fa-978a-1c3abec2782f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
