This is great! In my opinion, this should not only be a challenge for Flux frameworks, but generally replace todoMVC as the "go-to" example implementation.
This should reveal potential pain points a lot better.
This should reveal potential pain points a lot better.
I like the idea of a fuller common-comparison app (and even some of the requirements of this app), but not sure this is the right framing.
To me it appears to just be a cursable priority queue component. Such a component should be provided by a standard library, not implemented as its own app. Of course, this is a learning exercise so some leeway is afforded, but it might be even more effective to include extracting the core component into a reusable library as part of the challenge.
Also, what is a Todo app, but a priority queue?
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.
I really like this and hope that there are many entries.
"I'm curious about every solution's pros and cons, and I would prefer to discuss over evidence/artifacts instead of with platitude arguments."
best way to move a conversation forward I've seen in too long.