3 ms·
So, you're proposing MVVM.
by _pmf_ 10y ago
So, you're proposing MVVM.
- JustSomeNobody 10y agoNot necessarily. This could all be accomplished just be decoupling the view from everything else. It doesn't have to conform to MVVM, MVC, MVP, MVWhatever.
- achr2 10y agoThe part you're missing is that there is a huge grey area between 'model' and 'view'. So large in fact that all of these patterns where designed solely to help you draw lines in the sand between the pieces.
- JustSomeNobody 10y agoI would argue there's a grey area between the 'view' and the 'controller', but not the 'model' and the 'view'. The model is logic and data and has absolutely nothing to do with presentation. But, I will concede there are 1001 ways to interpret these patterns (MV*).
- achr2 10y agoAgreed - however, I wrote 'model' considering the binary separation that was suggested.
- Stengo 10y agoConvention does have its merits, though. Knowing a pattern makes reading and writing code much easier. So having structured, known ways to decouple views (or every other component for that matter) is valuable.
- JustSomeNobody 10y agoI don't disagree with what you're saying. But there are patterns where there's the View and ... everything else. It's a perfectly valid way of organizing code (for, admittedly, simpler code bases).