Skip to content

Comment on The M in MVC: Why Models are Misunderstood and Unappreciatedparent

Comments

My original answer was longer, but this is hopefully clearer. Small programs are often split: Input Parsing. Process. Output presentation.

We can think of MVC where the View is the output presentation. The Model does the processing. The Controller does the initial input parsing, determining which part of the process to pass control to.

The Controller as "dispatcher" or coordinator.

Thanks, this helps! Can you recommend any further reading? Or is it simpler than I'm thinking?

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.