I disagree that this is a good replacement for TodoMVC (not that I'm defending TodoMVC). Two reasons: 1. There is no end-user data input happening in this exa

I disagree that this is a good replacement for TodoMVC (not that I'm defending TodoMVC). Two reasons: 1. There is no end-user data input happening in this example, so we can't fully evaluate a potential framework's change tracking/dependency resolution/state update techniques. 2. The "low level" emphasis on controlling AJAX requests isn't a good fit for a lot of frameworks which may be un-opinionated about how data is loaded.