knockout.js - Knockout.js 和 Rxjs 有什么区别？

Question

有谁知道 RxJs 之间的区别和 Knockout ？对我来说，表面上他们似乎在试图解决同样的问题，构建一个事件驱动的 UI。但是对于两者都有过经验的人来说，它们有何不同/有何相似之处？你能描述一下他们的一些情况来帮助我选择吗？

Answer 1

史蒂夫(Knockout 的创建者)explained the difference在他的博客上:

I’m very familiar with Rx for JavaScript, having recently used itheavily on a big project, and in fact aspects of the design ofKnockout are made with my Rx experiences in mind.

The key differencebetween Knockout’s implementation of the observer pattern and Rx’s isthat Knockout automatically infers the associations and dependenciesbetween observables from regular procedural code without you having tospecify them up front though a special functional API. I wantedKnockout to use regular procedural/imperative-style code as it’s morefamiliar and approachable for most developers.

Another difference isthat Rx is optimised for composing streams of events without state. Atfirst I was enthusiastic about this and its functional purity, butafter some time it felt increasingly like I was jumping throughawkward hoops and had to invent extra ways to simulate state to manageUI commands efficiently. That’s why, in Knockout, all observables canbe treated as stateful - for example you can always read their latestvalue (which is cached, by the way - it doesn’t recompute until theunderlying data changes).

Rx goes further than Knockout into advancedways of composing event streams, whereas Knockout goes further than Rxinto UI development, letting you bind its observables to HTML DOMelements and templates and manipulate them any way you want. Rx isgreat at what it does but turned out not be be exactly how I wanted tobuild rich UIs - hence the design of Knockout.