search

blyscuit / Surveyer

0 stars 0 forks source link

Is ViewModelBinding really necessary? #3

Open edgarss opened 4 years ago

edgarss commented 4 years ago

It adds unnecessary complexity using datasources and ViewModel bindings. is there a reason for not using Protocol delegate pattern?

It looks like you are trying to do reactive programming but not going all the way.

blyscuit commented 4 years ago

I came upon this pattern after trying several MVVM pattern, including Protocol pattern. At the time I found Protocol pattern to be a little messy on both ViewModel and ViewController. This pattern solves the problem of having large lib of RxSwift (reducing build time by a lot) and giving control over how we would like observable to behave. As you said, it's like Reactive half-way but I found the code to be more readable, condensing binding in one section and appealing to anyone with Rx background. I believe it reduce time to come up with a reasonable name for Protocol methods and not having to know ViewModel to understand what data to bind. (solvable by having a pattern that everyone follows).