Hi Hendy Christianto,
When we refactor something, we cannot escape having to check somehow that the project is left in a consistent state.
If you have people working on a module as a product, and it’s up to them to integrate that module back into the project, it will be their responsibility to make…
Hi kingnight, that’s a good question! I must have placed it by mistake when configuring the project. I don’t think it’s useful, I’ll double-check and remove it when I have a chance.
The main reason for doing something like that, would be to diminish the amount of conflicts you get with your versioning system, right ?
I think that if you have a single workspace and multiple projects (like I propose), the kind of conflicts in git would be the same as if you had multiple…
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…
Hi Edison, a reason I could mention out of the top of my head is that your structs are nesting and creating exponential memory growth as the copies stack.
Imagine a Struct that contains a list of values, in which the same Struct type appears. E.g. a Node with a history of previous Nodes. Each time you add an instance to that list, you keep the…
Hi Amir, thanks for taking the time to read the article!
It does make sense. I am doing that in my current project. I think it’s important to know that if you start using it deeply, you’re married to it and it will be really hard to change your mind later.