Introducing React Native [video]

Post by brandonbloom » Sat, Jan 31, 2015, 5:59 PM UTC

seanmcdirmid wrote: post #108

brandonbloom wrote: post #69

Earlier quoted context omitted.

Having worked on production software with both WPF and React, I can tell you why React's "data binding" approach is categorically different (better, in my opinion) than WPF's. Like many abstractions in WPF, bindings have a "shadow world" feeling, where they are their own little isolated DSL. With the React model, "bindings" are just JavaScript expressions. Sure, with WPF you can overload operators and create "Express…

Right, WPF's declarative databinding support is separated from imperative semantics, even if they can interact a bit (a databinding relationship can be formed and destroyed imperatively). But I've moved away from WPF to Glitch, which doesn't have that problem: all code runs in the same world, with dependency tracing, re-evaluation on dependency change, and logging to support rollback as needed. In that case, now I'm…

Post by seanmcdirmid » Sat, Jan 31, 2015, 11:33 PM UTC

brandonbloom wrote: post #191

seanmcdirmid wrote: post #108

Earlier quoted context omitted.

Right, WPF's declarative databinding support is separated from imperative semantics, even if they can interact a bit (a databinding relationship can be formed and destroyed imperatively). But I've moved away from WPF to Glitch, which doesn't have that problem: all code runs in the same world, with dependency tracing, re-evaluation on dependency change, and logging to support rollback as needed. In that case, now I'm…

It doesn't have to track dependencies at all, but it is certainly still incremental. Maybe you should study it before judging it.