4 ms·
> the problem with MVC as given is that you end up stuffing too much code into your controllers > [Under MOVE, e]vents are used to join all these components to
by kazinator 7y ago
> the problem with MVC as given is that you end up stuffing too much code into your controllers
> [Under MOVE, e]vents are used to join all these components together safely.
The problem with events is that you put all interactions into events, creating a labyrinth of ad-hoc protocols.
Events are messages, and messages are just methods in disguise: worse ones, that don't have a call stack you can inspect.
Under this MOVE, someone will sooner or later hit the problem of wanting the V to manipulate the M in some way that O doesn't support, and will just end up creating some hack whereby a whole chunk of the M state (perhaps all of it) is downloaded via some stream of events, edited, and sent back via another stream of events.