It's not directly related to Flux, but it's worth thinking about. Way before we outsourced every project's architecture to this week's framework du jour (only

It's not directly related to Flux, but it's worth thinking about. Way before we outsourced every project's architecture to this week's framework du jour (only to complain about it later), I worked on many projects with somewhat ad-hoc architectures in an agile-like manner. We knew of MVC, but we didn't necessary reach for it explicitly. Instead, we just tried to extract domain/business logic out of the desktop UI layer as often as we could, and called it good. Instead of constantly worrying about cramming everything into small conceptual boxes, we just wrote code and decoupled what we thought might change. Flux reminds me of those times because it is far less prescriptive than MVC. There's a certain freedom to just letting the code grow (assuming you prune it as you go), rather than constantly worrying about whether this feature should go in the model/presenter/controller/whatever. A caveat: I'm almost certain part of the clarity comes from the delivery mechanism being far more conceptually sound than HTML/CSS/JS.