So I found a limitation with the android API, and would like to know how you use to overcome it... CompoundButton's change listener is always called, regardless on if you change it programmatically or the user changes it...
What does people in rxandroid do with this limitation? Do you create you own button implementation?
CompoundButtons are a bit of a pain. For example I wanted a CompoundButton that would only toggle the state programmatically, not when it was tapped. I had to extend the class to get the effect when I wanted.
so, I was talking with a guy that has been doing android dev past years and he spoke against Rx because of not being able to decouple business logic from the activity, this is, that Rx is more a framework than a library, so if you use Rx, and it gets unsupported, you will have to change all your code
You use it just like you use a for-next loop. It has many uses but it's not a framework. Or compare it to a design pattern. Hell, it's pretty much a extended version of the classic observer pattern, or publisher/subscriber.