S-array

> MobX strives to implement transparent reactive programming, where the way you access, update and transform values works exactly like it would with regular objects. S.js has a worse learning curve. Hardly: reactive values are get/set functions, and you create new ones with S(() => ...). That's it. MobX's attempt at transparency yields inescapable and surprising corner cases. > Redundant computations are computed; [...] even though the completed() computed isn't used anywhere, the reduction is still being recomputed every time todo state changes Incorrect. The todos binding is an SArray not a regular array [1]. See my modified version where I log the events to the console [2]. [1] https://github.com/adamhaile/S-array [2] https://codepen.io/anon/pen/KQyOyZ