haxedci-example VS haxedci

I have written tutorials and code examples over the years that tries to show, from the programmers point of view, that you get a sense of clarity and control with a DCI Context that is highly local and expresses the mental model of the user better than any other paradigm. It is something that needs to be experienced as well as understood.

Also, this tutorial is quite ok to understand the concept, Haxe is not too far away from javascript/typescript: https://github.com/ciscoheat/haxedci

It's difficult to find information about actual DCI implementations nowadays, a shame since understand it will make you a better programmer, guaranteed. But having spent 10 years researching about it, I can hopefully answer any questions you might have. A tutorial with code is available here, as well: https://github.com/ciscoheat/haxedci

DCI (Data, Context, Interaction) gives us a way to true OOP, but it cannot simply be explained in a comment section. You can scratch the surface by checking out this tutorial, and I'm available to answer any questions.

DCI takes this a step further by making the mental model a first class entity in the system. MVC is more atomic, DCI is about behavior. They complement each other. It's hard to explain briefly, and a whole another topic, but I've written a tutorial on github if you're interested.