On Wed, Oct 09, 2019 at 03:29:51AM -0400, George Neuner wrote: ... ... > One of the issues I have with MVC is the way it typically is > presented: data flow in the tutorials tends to be exaggerated and > overly complicated, and the explanation typically revolves around DBMS > and graphical UIs that simply aren't relevant to it. > > As a design pattern, MVC dates from the 1960s, from the era of CRT > display/edit form-based applications. The View and Controller > historically were integrated, and the "Model" was a memory cache of > one or more data records.
That's what always bothered me about MVC -- the idea that the View and Controller should be separate. The idea of interpreting user actions (clicking and typing on a screen) without knowing details of the view (which governed where he clicked and typed) seemed absurd. Separating the model made sense. Especially because you might need very different Views on different terminal devices. -- hendrik -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/20191009142009.r4pquot7qddyvjzs%40topoi.pooq.com.
