I have a suggestion to this, but I don&#x27;t know how to get it out there. I can&#x27;t build a library because the point is to not depend on libraries.<p>My suggestion is that if your going to build an application in the browser, your project needs an architecture that will last beyond today&#x27;s libraries and tooling. You want to recognize what&#x27;s unique about your app and express those parts without touching the DOM or network, even if they seem trivial now.<p>My particular favorite way to do that is using an event bus to create a catalog of custom&#x2F;domain-specific events, with views emitting operation- or command-like events and internal models emitting new states. This is basically the important part of Flux without the special concepts (stores, dispatcher) that you may be fine without, and is already available in jQuery, Backbone, node&#x27;s EventEmitter, and many other libraries out there.<p>React and immutability and the rest of Flux are all very reasonable next steps if somehow you come to need them, but you are likely not spreading your UI development across hundreds of engineers. Unnecessary new stuff is just going to steer your conversations towards libraries and away from your domain.