Leandro Pérez
Jul 4, 2019 · 1 min read

Hi Ronan Rodrigo Nunes, I’ve just realized I never replied to your question. Sorry about that!
I think you are right, it would indeed be really hard to abstract it away. Once you are married to RxSwift, your architecture is permeated with it and it is virtually impossible to make it independent of it.
So, in a pure sense, using it would go against that principle mentioned in Uncle Bob’s article.
Having said that, I think if the other aspects of using Rx may be worth this compromise. You can view it as a very low-level framework you are buying. But it’s hard for me too to compromise these things when I think in purists terms. It’s hard to know where to draw the line.
I think in the end, it’s a matter of what you and your team are comfortable working with.

Thanks for reading and commenting, and again, so sorry for the extremely late reply.

    Leandro Pérez

    Written by

    Software Engineer, coding since 2001. I have done plenty of work in iOS with Objective-C and Swift.