Timeline for OOD vs MVC; Live Objects vs Everything in Database
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 7:06 | comment | added | candied_orange | MVC doesn't have an opinion about encapsulation or databases. It cares that you have three modules each focused on their responsibility. Anything more is simply from a particular implementation of MVC. | |
| Jun 10, 2020 at 16:50 | comment | added | Jason K. | You would be better served asking more specific questions against more concrete examples. This site is intended for questions and answers, but you are attempting to use it for a more general consulting purpose which is not its intent. | |
| Jun 10, 2020 at 9:37 | answer | added | Robert Bräutigam | timeline score: 1 | |
| Jun 10, 2020 at 8:51 | review | Close votes | |||
| Jun 15, 2020 at 3:01 | |||||
| Jun 10, 2020 at 7:42 | answer | added | Christophe | timeline score: 3 | |
| Jun 10, 2020 at 4:45 | answer | added | Kain0_0 | timeline score: 3 | |
| Jun 10, 2020 at 2:54 | comment | added | Theraot | "a class for each of the item" what? I hope you mean object, not class. Anyway, why does each camera need its own timer? Perhaps borrowing the idea of a game loop can be helpful. By the way, yes, there are reasons to give up encapsulation. At least the conventional OO kind of encapsulation. Submitted to your consideration: Data-Oriented Design. You may also benefit from a functional core. | |
| Jun 10, 2020 at 0:21 | review | First posts | |||
| Jun 10, 2020 at 16:50 | |||||
| Jun 10, 2020 at 0:20 | history | asked | Daniel Gordon | CC BY-SA 4.0 |