The improvements in these tools aren't supposed to push us to create novel projects. They're supposed to get out of our way. Some do better than others, and some paradigms can be more helpful than others. It makes sense that we have competing ideas and competing frameworks to implement those ideas.
Some projects get a bit flashy and buzzwordy, it's true. Bacon.js [0] always sticks out in my mind as a prototypical example, though I think it's tongue-in-cheek.
I try not to let that flashiness get in the way, though. The fact is, Bacon.js is useful to me, when I try to make beautiful and efficient code to render beautiful and efficient HTML. Their homepage doesn't change that. React's performance is impressive, and may be important to me; ditto with Flux and code readability. And the theories underlying those libraries (DOM diff and unidrectional data flow) are important too, so I know why I should expect them to be better.
Some projects get a bit flashy and buzzwordy, it's true. Bacon.js [0] always sticks out in my mind as a prototypical example, though I think it's tongue-in-cheek.
I try not to let that flashiness get in the way, though. The fact is, Bacon.js is useful to me, when I try to make beautiful and efficient code to render beautiful and efficient HTML. Their homepage doesn't change that. React's performance is impressive, and may be important to me; ditto with Flux and code readability. And the theories underlying those libraries (DOM diff and unidrectional data flow) are important too, so I know why I should expect them to be better.
[0] https://github.com/baconjs/bacon.js/