I have been using it everywhere, but sometimes I l...
# rx
j
I have been using it everywhere, but sometimes I look back and ask why
t
billy: that's interesting because I have observed the opposite. Unless you are using a lot of blocking, subjects, and breaking monads, I've found Rx to eliminate boilerplate quite a bit.
j
Well there is a point there I admit, but I generate alot of client code for android and ios and service to service clients, I always generate it with calls returning observables, because I want combinability in everything.
In the end its 80-20 only 20 percent of calls are ever really combined, but so be it, I cant design that up front.
But the boilerpplate I was really mentioning is the addition of things like MVVM
In the end I could code in simple forms and such about the same thing in less code, heck I have been doing it for 20 years.
The operator head scratching and extra code for MVVM seems like its unnecessary for many things, I am trying to find the optimal amount of rx in an application but for now Im kind of shotgunning it everywhere to see where I feel its not really needed later