MVC and Object Oriented designs have consistently been misapplied to various runtimes since their introduction and proper use in systems like Smalltalk and Self

MVC and Object Oriented designs have consistently been misapplied to various runtimes since their introduction and proper use in systems like Smalltalk and Self (I'm like a broken record if you know me at all). The MVC patterns in Ember and Angular have never made any sense. The only good thing about Angular are the directives. They made a big mistake in adding Services, Controllers, Filters, Routes and all of these super opinionated, bulky, slow things that aren't always needed. Ember suffers from similar bulk but the DOM/data binding is nowhere as elegant as Angular or React. Another great data-binding abstraction is d3. d3 is great for working with and displaying large data sets. It also does the right thing and keeps it's functionality simple. It's not trying to be the only abstraction in your tool belt. I've been using a home-grown abstraction for data retrieval and test mocks that has be loosely inspired by Angular's Services, but is much more functional in design. I'll release it in a few months once it has survived a few more iterations on this product I'm working on. It's called getIt. getIt and React. Get it? Every time someone sits down and decides to build THE ONE SYSTEM TO RULE THEM ALL... it fucks up... Mordor, the Soviet Union, Angular, whatever, same rule applies. :)