Helge Heß on Nostr: npub1t5m0n…59guy Generally true, in the ctx of MV*C* is not that ambiguous 🙂 The ...
npub1t5m0nvfy3ukegy92tv73mvfn95ku9trys28uwd8hmndgj956wzpqz59guy (npub1t5m…9guy) Generally true, in the ctx of MV*C* is not that ambiguous 🙂 The term "MVC" is quite overloaded though, despite proper work backing the term. This is a nice article in that context: https://blog.metaobject.com/2015/04/model-widget-controller-mwc-aka-apple.html
For models my general rule of thumb is: Imagine you build an app and you need to provide both, an HTML interface and an AppKit UI. The things you can share between the two is business logic and goes into the model layer.
The immutable thing you describe sounds more like a DTO.
For models my general rule of thumb is: Imagine you build an app and you need to provide both, an HTML interface and an AppKit UI. The things you can share between the two is business logic and goes into the model layer.
The immutable thing you describe sounds more like a DTO.