doing modern scalable full stack projects with .NET / NodeJS everyday for 6+ yrs!
taking full responsibility for any 'crash tactics' approached
No blogs yet.
I think the way is to be reactive for two-way data binding implementation. MobX and knockout.js proves that. Pub/sub pattern seems to fit in general. The Observer and Observable could provide a generalized mechanism for push-based notifications, as core of two-way data binding, which also known as the observer design pattern. And Rx are known to be the battle tested implementation of the pattern. Observable object represents the object that sends notifications ( the provider ), and the Observer object represents the class that receives them ( the observer ). I will not try to implement the wheel, my theoretical optimism says that things should be obvious :) Great egghead session should help with code: https: //egghead.io/lessons/rxjs-creating-observable-from-scratch
There is a number of 'fiddlers' around the web for doing quick prototyping, such as jsfiddle.net, codepen.io, es6fiddle.net... Now, even https://fiddles.io/ exists... they gathered a respectful list of web-based prototyping pads there, for different languages. I can see that there is new great updates coming into codepen.io each day, so maybe other developers too much love the chrome console, as much as I am?